C-Beats

No real idea how that would be the case since I'm using the same control as Default to display them. There may be some underlying event that is ticking on the main thread in Default that for some reason my theme isn't tying itself to that is causing it. It's hard for me to test because I can't replicate the reported issue at all.

Believe so

This happens when the CRC record on the DB metadata file doesn't match the CRC on the file. We have to run a script to correct occasionally. I'll make the team aware that the process needs ran again.

Personally I would just hide the sidebar (Ctrl+S). If you need to navigate away press it again or use the combobox drop down that appears when you hide it. Don't currently have any plans to do so, not sure if keyboard navigation would work doing something like that either. Could play with the panel used and see if you can get it on your own, but I have enough stuff yet to do that I wouldn't be able to look into it for a while.

Can you post up a screenshot of your Windows display settings so I can do my best to recreate your situation and see what we can do to correct? Curious if it's something to do with what screen is left or right or something dumb like that. Also what is your scaling on the two monitors?

The views themselves are all driven via the XAML files. The xaml files have a "ViewSelector" that in MainView is the visible control, and in the other files tells the view what item is currently selected. I then use Style Triggers to show/collapse the appropriate setup. The plugin is only for that ViewSelector control. Theme also has the ThemeValues file that I'll use to help modify/tweak the theme to the users liking. Can change theme colors and it stores what view you were in when you closed LaunchBox so that when you open it up again you don't have to manually change back to the view you actually want.

For those willing to help us test this out. The latest release of my Omni theme utilizes this functionality for it's view selector switch. To test download and apply the theme from the downloads section (Theme manager doesn't have the version with the plugin) and run LaunchBox. If all goes well you simply won't notice anything different and can use the theme (and LaunchBox) normally.

Omni v1.1 has just been released! IMPORTANT: This version of Omni now requires LaunchBox 13.6 Beta 1 or newer! With this new version of Omni we begin to see the grand scheme of the theme come into view. Omni is the first LaunchBox theme ever to have THREE content views! In the upper right of the main view there is now a view selector that allows you to switch between the following views: Image View - Traditional LaunchBox Image View Details View - DataGrid List View (Traditional LaunchBox List View) List View - A dynamic list view that looks similar to Beats list view when space allows, but when shrunk looks like the List view I utilize in Airy/Steamy. Next version I'll start tackling GameDetails and making it work better with varying widths, as well as pop out.

Are the files changing or just the emulator? You can change the games emulator without reimporting them.

Has nothing to do with the set you have. You have to point the wizard to the 0.255 version of MAME you installed (or let us download it for you)

Have you checked if notifications are disabled in the operating system, or if you have Windows auto-hiding ours?

There is a "RotationAngle" (double) and "RotationAxis" (Vector3D) that can be styled on the FlowContext that rotates the entire item in the FlowControl. Typically you want "0,1,0" (Up) or "0,0,1" (Forward) to be the Axis

Yeah recent is the Top X games sorted by Date Played (if one exists) or Date Modified (if you haven't played it). We probably need to take a look at using Date Added instead for that logic. I believe we have a note internally about it, but it hasn't made it into a build yet. I'll check with the team though.

Your XAML wouldn't work for several reasons. The FlowModel doesn't belong in the FlowControl's DataContext, it goes in the FlowTemplate. If you're looking for syntax on how to use those bindings Faeran's 3-Dimensions theme uses it pretty heavily.

Don't believe any Big Box code was touched in 13.4/5 release so I'm not entirely sure what would cause any change to what you're seeing. Does reverting to 13.3 correct? Also could you take a pic of your Platform Category tree in LaunchBox so I can see a bit better what you mean?

This is a known issue with old versions of MAME, or non official MAME emulators. The fullset wizard gets the listxml command from your MAME executable and if it isn't an official MAME emulator or is too old the XML schema it spits out isn't formatted in the way the app expects and this happens.

This is a known bug (been around for a long while) that appears sometimes but I've not been able to track down a cause as it happens so randomly. If you run into an process that reliably replicates the issue please let us know.

LaunchBox uses relative paths so to be able to simply copy/paste the folder from one location to another it's recommended that all emulators be installed in an "Emulators" folder within the root LaunchBox folder. If doing this (and the emulators are portable) then they "just work" after to copy to the new location.

Resets all Big Box settings

You can set that up in Big Box controller section. Just turn off "Use All Controllers" and then set the controller you want it to use.

Ah yeah I know what this is. I can address it in the next release. It won't affect your ability to use the app in any way.

You can disable the 3D model in Big Box settings

The option only shows in Image View. The hotkey for it is Ctrl+R

Yeah, this theme was a bit challenging regarding vert space because of that, but I do enjoy having it. I could probably look and see about adding a visible setting in the ThemeValues file that can be changed to turn it off/on

Omni View File "Omni" is a prefix meaning "all", in that regard this theme strives to do "all the things" in ONE theme! Omni has both a content view selector and game details selector that lets you choose the content view and details view that looks best to you. There are 15 different configurations to choose from! All of these settings are saved in a ThemeValues.xaml file that allows you to customize them EVEN MORE! NOTICE: Omni requires LaunchBox v13.6 or greater! Submitter C-Beats Submitted 06/01/2023 Category Custom Themes