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.
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.
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.
Believe the CTC lets you choose between "Active Game" binding and "Selected Game" binding. Selected is updated instantly, Active is delayed. Any additional elements displaying information about the game being hovered over should be using the Active binding to help reduce the delay you're seeing. There could be other factors affecting you that I'm not aware of, but this typically is the most egregious cause for the delay you're showing in the video.
Also worth noting that Windows itself will push any RAM usage the app (or any other app) is using to the page file if it isn't the active application and the OS needs the memory the app is sitting on. This act of moving it to the page file the first time IS slower but after that first time the memory stays in the page file until you return to the app and so wouldn't affect performance after that.
Biggest difference between the two themes you see are the use of the "Active" and "Selected" game bindings. First theme is using the one that is updated immediately and so every time you move it updates every element in the theme. The second one is using the delayed one that only gets updated after you've stayed on the game for a second. Because the second isn't trying to load a bunch of images/videos instantly every time you move in the list it works faster.
Just so you are aware @Madhead there is both a side bar filter AND a quick filter for custom tags and so you can use either when trying to navigate to games with a specific tag