eatkinola

You need to go into BigBox settings and change the game and platform views to wheel view #4, which will display platform/game clear logos in the wheel. You can map a keyboard shortcut to quickly cycle through views, or you can go into BigBox settings each time.

UPDATED to v1.5 - see changelog on download page

UPDATED to v1.9 -- see changelog on download page for details

UPDATED to v5.9 -- see changelog on download page for info

UPDATED to v1.6 -- please see download page for changelog

FYI recently switched from google drive to syncthing which was pretty simple to setup, I think. So far I find syncthing to work better than google drive, and it let's you create your own private cloud. I use it on my local network only, but I'm pretty sure you can also use it over a wan. It works across linux, windows, and android. Also with syncthing, the only thing that limits storage space is the drives I have, so now I sync not only my game saves but also my LB data and media.

Awesome! I also practice the "die and retry" style. It's the best way to learn.

I can write the code for you. If you don't mind, I'll integrate it with my themer library and you can use it from there. The library already has some logic for handling platforms with different naming conventions, e.g., some users prefer "Nintendo Entertainment System" while others prefer "Nintendo NES". I have a way to insulate from these differences. I'll pm you.

Hey @viking looking forward to see what you're putting together. I'm pretty sure you'll need a converter to do this. Using data triggers would work, but it would lead to very messy repetitive xaml and not the clean centralized code you're trying to write. I cannot think of a clean, xaml-only way to do this (maybe someone else can). This example from stackoverflow looks promising; you can define stuff in an xaml resource file like you want. You would need to code a converter, however would be a pretty simple piece of code. https://stackoverflow.com/a/20280045 Then your xaml view file would say something like this: <UserControl xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"> <UserControl.Resources> <ResourceDictionary> <ResourceDictionary.MergedDictionaries> <ResourceDictionary Source="pack://siteoforigin:,,,/Themes/VikingsCoolTheme/Views/Styles/Colorful.xaml" /> </ResourceDictionary.MergedDictionaries> </ResourceDictionary> </UserControl.Resources> <Canvas Name="Canvas"> ... <TextBlock Text="My colorful text" Foreground="{Binding ActivePlatform.Name, Converter={StaticResource PlatformColorConverter}}" /> ... </Canvas> </UserControl> Your xaml resource file Colorful.xaml would look something like this: <ResourceDictionary xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" xmlns:colorful="clr-namespace:Viking.Colorful;assembly=Viking.Colorful"> ... <colorful:PlatformColorConverter x:Key="PlatformColorConverter" /> ... <SolidColorBrush x:Key="Color_Atari 2600" Color="Red" /> <SolidColorBrush x:Key="Color_Atari 5200" Color="Blue" /> ... </ResourceDictionary> You would place the Viking.Colorful.dll (which defines the converter) in the theme's Plugins directory. I've not tested any of this and might have made some typos, but something like it should work. P.s. The stackoverflow solution will need some tweaking since you won't be adding your color definitions to the App.xaml but rather a separate xaml file. You'd have to reference that xaml file specifically, but I'm sure it could be done.

Whoa quite a few of these poll items are really getting into the weeds, which is a testament to how feature-rich LB /BB has become. Great job!

Honestly haven't tested Nostalgia in a while. A few months ago, some memory leaks were brought to my attention, and I've slowly been isolating those leaks. It's taking a long time because I have to let a theme run in attract mode for days on end. I've identified 3 of 4 (I think there are four total) leaks, and once I plug them I'll double back and take a look at Nostalgia and my other themes.

Updated to v1.5 -- see download page for details: https://forums.launchbox-app.com/files/file/1619-wootlauncher/

Thanks for the screenshot -- looks correct. I'll do some digging and if a fix is needed include it with the next theme update. Hmm, I'm surprised it's not remembering your setting. Is there perhaps another BB setting keeping it from remembering your image choice for a particular platform. Is the image choice you are making remembered when using other themes?

Thanks a bunch @qu1r0s! @EduInmigrante: Development has been slow lately owing to work stuff, but these translation mods are slated for the next update.

P.s. I'll have to include these changes in the next release of the theme, as these translations are bundled in the Ao.Bigbox.Themer plugin.

You can edit a line in Views\Styles\Nostalgia.xaml to add the broken icon: <Style x:Key="NostMetadataIcons_GAME" TargetType="aop:GameMetadataIcons" BasedOn="{StaticResource NostMetadataIcons}"> <Setter Property="FieldOrder" Value="GameGenre,GamePlayMode,GameAgeRating,GameStarRating,GameBroken" /> </Style> Possible values for fields include: Yes, the image displayed on the bottom is the main game image you selected for the game's platform. To change this, go into this view for a particular platform then press the hotkey you setup to cycle through these images, e.g., clear logo, box front, etc. You can assign a hotkey in the BB settings menu for keyboard mapping, i.e., the mapping for "Switch Image Type" (in English). I don't speak Spanish and did the translations myself using Google. Not ideal, and I'd appreciate if you'd take a look at the translations (hidden below) and provide suggestions.

Viking and I discussed a very similar (the same?) issue in the XAML Tips & Tricks thread. To handle various resolutions and aspect ratios gracefully, I had made two plugins: (1) AutoscaleTextBlock, and (2) DimensionW3840Converter. There are examples for both of these on page 30 of that thread: https://forums.launchbox-app.com/topic/28698-xaml-tips-and-tricks/page/30/ Check it out -- might solve your issue. I didn't look at the stackoverflow examples closely, but my approach with the converter seems similar.

Updated to v1.4 -- see download page for details. Changes are mostly minor, but the deployment is different. The download file is now called Ao.Bigbox.Dropins and as before contains WL and also additional plugins (which also as before are disabled by default). Enjoy. https://forums.launchbox-app.com/files/file/1619-wootlauncher/

Great. Please review the PDF manual bundled with the download. It should be ready-to-go out of the box for the common emulators, but you might need to define button mappings in one of the config files.

It'll work with either LB or BB.

There's a plug-in for that. If you're interested or have questions please see and reply in this thread:

Updated to v1.3 -- most notably theming additions, including the ability to integrate with BB themes for a more cohesive experience. An example of this with FluxCRT is posted above. Also, WL should be ready to work with the multi-keyboard-button config thingy Jason is working on with his pause screens. I beat up on it quite a bit, but please let me know if you spot any errors.

.NET 4.7 works on my "antiquated" Win7 boxes.

When I've wanted to hide a platform, I just remove it's xaml file from the data folder, or place it in a subfolder I just call 'Inactive'. That works well for me. It'd be nice to have a little toggle in LB to show/hide a platform and probably (?) a simple addition, but I've made do fine without it.

You'd probably want to pause the emulator before sending the other commands via autohotkey. Then, when you are done sending commands, unpause the emu. AHK can also issue the pause/unpause commands, so this could all be seamless.