Jump to content
LaunchBox Community Forums

eatkinola

Members
  • Posts

    801
  • Joined

  • Last visited

  • Days Won

    13

Everything posted by eatkinola

  1. Thanks for the update, was scratching my head over that one. Glad to hear it works! -- I didn't design or test it with marquees in mind. Unfortunately, I cannot think of any way to further optimize the video engine. Could it be related to your CPU or video card? Running videos can be pretty taxing, especially if another application is also running. Might it work better if you used smaller video files for the marquee?
  2. Here's a quick demo of WL integrated with my FluxCRT theme. I use the same bezels for retroarch as I do in FluxCRT, so the transitions are pretty seamless I think. This is my first time uploading a video here so hopefully it's okay. My_Movie.mp4
  3. Thanks for the example. I tried to slice it every which way but did not detect a problem with muting videos. Perhaps I'm not fully understanding the reported problem. Appreciate your pm; I don't use discord, so if whoever reported this problem to you wants to post additional details here on the forums that might be helpful.
  4. You're referring to Ao.Bigbox.Themer? Please point me to who reported this so I can get more details and perhaps an example where it does not work?
  5. Added ability to "theme" WL; this can be integrated with BB themes, e.g., pause menu for Refaktor: ...compared to the built-in/default theme for WL: Will work on adding support for multiple keyboard bindings, to work with the upcoming BB update.
  6. @viking: here's an example of what I mentioned ^^ -- aox:DimensionW3840Converter is the key. You specify the dimension assuming 4K display (3840 pixels wide), and the converter scales this dimension according to the actual display width. This is an example of one of my styles used to define a storyboard where something flies in from the left side of the screen: xmlns:aox="clr-namespace:Ao.Bigbox.Converters;assembly=Ao.Bigbox.Themer.v3_9_3" ... <aox:DimensionW3840Converter x:Key="DimensionW3840Converter" /> ... <sys:Double x:Key="AO3840_FlyinOffsetLeft">-500</sys:Double> <sys:Double x:Key="AO3840_FlyinOffsetLeftBounce">40</sys:Double> ... <Storyboard x:Key="AOSelectedFlyin_L" TargetName="GridFlyLeft"> <DoubleAnimationUsingKeyFrames Storyboard.TargetProperty="RenderTransform.(TranslateTransform.X)"> <LinearDoubleKeyFrame KeyTime="0:0:0.00" Value="{Binding Source={StaticResource AO3840_FlyinOffsetLeft}, Converter={StaticResource DimensionW3840Converter}}" /> <LinearDoubleKeyFrame KeyTime="0:0:1.70" Value="{Binding Source={StaticResource AO3840_FlyinOffsetLeft}, Converter={StaticResource DimensionW3840Converter}}" /> <LinearDoubleKeyFrame KeyTime="0:0:1.85" Value="{Binding Source={StaticResource AO3840_FlyinOffsetLeftBounce}, Converter={StaticResource DimensionW3840Converter}}" /> <LinearDoubleKeyFrame KeyTime="0:0:1.90" Value="0" /> </DoubleAnimationUsingKeyFrames> </Storyboard>
  7. I do something similar in one of my themes. It requires a converter when is also in the themer dll. I'll send you an example later when home.
  8. Great! About the vertical scroll text, you mean controls:ScrollableTextBlock? -- That would require some customization of that control which resides in the Unbroken.LaunchBox.Wpf DLL. Alternatively, a new custom control could possibly be made for Ao.Bigbox.Themer. I wonder if one of those auto-scaling solutions posted in stackoverflow that you mentioned would be helpful; I'll have to take a look.
  9. Sometimes you want padding around a TextBlock to space it a certain way, and if so you'd also want that to be automatically scaled.
  10. Hey @viking. Try the AutoscaleTextBlock in Ao.Bigbox.Themer: 1. Download latest version of themer plugin: https://forums.launchbox-app.com/files/file/1747-aobigbox-customs/ 2. Place the plugin in your theme's Plugins directory. 3. Add this to your xaml file: <!-- included near the top of the xaml file --> ... xmlns:aoc="clr-namespace:Ao.Bigbox.Controls;assembly=Ao.Bigbox.Themer.v3_9_3"> ... <!-- example use --> <aoc:AutoscaleTextBlock Text="whatever" FontFamily="MyCoolFont" FontWeight="Normal" Foreground="Cyan" TargetFontSize="32" TargetPadding="0,8,0,8" TargetScreenHeight="2160" /> The key properties are the TargetXxx properties -- they let you design to a target screen height, and the actual font size will be scaled automatically based on the actual screen height.
  11. True dat. Viewbox and Grid gets you 95% of the way to resolution independence. I created AutoscaleTextBlock for the other 5%.
  12. Certainly, I'd be happy to share it. I recommend let's give others time to chime in as they might propose a better solution before embarking on using my solution. I'm at work now anyways and cannot post the library and code examples from here.
  13. When I ran into this issue, I created two controls called AutoscaleTextBlock and AutoscaleListBox (for text lists). On these controls, I can set a TargetFontSize and TargetScreenHeight and design to these parameters. It will then scale the font size according to actual screen height. The solutions you reference on stackoverflow look very interesting and more generalizable than my approach. I don't have time to try out those solutions now, but I do have something that works if those ideas aren't effective.
  14. Cool, hope you like it. I just submitted it for the BB theme downloader; hopefully it makes the cut.
  15. UPDATED to v5.8 -- see changelog on download page:
  16. Yep, will do -- that feature is actually working now on my dev version, and I'll include it in the next update.
  17. Hey it's no problem at all. I really appreciate you hanging in there and helping figure this out. I'm sure someone else would have raised this issue. Now we know to be on the lookout for it, and I'll add a bit of logic to the codebase to detect and log this problem when it occurs for someone else.
  18. The "WL" log looks odd; never saw this during development. You see how the GENERAL SETTINGS and EMULATOR CONFIGS sections of the log are showing up twice? The rest of the logged actions are also happening twice. It looks like there are two copies of WootLauncher either in the LaunchBox\Plugins folder or LaunchBox\Themes\[Theme]\Plugins folder. There should be only one of these at it should be placed in LaunchBox\Plugins. Please check on that.
  19. I think WL will generate the log file regardless of whether or not you turn on "Logging" in LaunchBox's options, but I don't recall off the top of my head. I usually have logging turned on anyway since I've been developing and testing a lot recently.
  20. That's correct, except for pressing Alt+A (I don't think) currently closes the pause menu; that's the feature I mentioned adding based on your feedback. Yep, it does sound like a disconnect. Via the pause menu, can you save/load game states? WL should generate a log file when you use it. Perhaps it would help if you sent me that along with the WL config files for retroarch you are using (if they differ from what's in the download). You said you disabled other AutoHotKey stuff, so that shouldn't be interfering. I don't think it's a timing issue, but there is a way to extend the delay between keypresses to test that out (I think I documented that in the PDF). Anyway, perhaps send me your log and possibly the config file I mentioned. Agreed, that'd be a good addition. Thanks for bringing it up. Mostly correct, except BigBox does not deal in button combos; you just map individual buttons to individual actions. WL aggregates button inputs to interpret combos.
  21. Okay I think I understand. You are using the same hotkey to both bring up the WL pause menu and pause retroarch? That will cause issues, because the first thing the WL pause menu will do when it is shown is pause the game using the mapping you defined in RA -- so using to same key mapping for both WL's pause menu and RA's pause/resume function will pause and then immediately unpause the game again. Does that sound to you what could be happening? The issue with closing the pause menu: currently, the WL pause menu mapping (keyboard or gamepad) does not actually close the pause menu -- the only way to do that is to select the Resume button. Now, I could probably add this feature so you could simply pause and unpause with the same keyboard or gamepad combo, configurable in the WL config. This also gets back to the problem of mapping the "pause" key on your system to both RA pause and WL pause; that will not work. You have to have separate mappings and let WL send a separate pause command to RA, as defined in the WL config file for that emulator/core (e.g., currently "+p" is mapped to pause/resume for RA). Yes, that is sort of correct -- WL will use the gamepad mappings for SELECT, BACK, PAGEUP, and PAGEDN as configured in BigBox. However, as of WL 1.2 you can override this mapping by editing keys in the GENERAL section of Ao.Bigbox.Dropins.dll.config. I really implemented this "override" feature so people without BigBox could still use WL. I think I described this in the updated PDF manual, but let me know if it's unclear. The "PageDn^PageUp+Up" syntax was something I just made up myself to allow you to configure button combos.
  22. Thanks Jason. The whole idea of a theme manager is really great. I tried a few times to upload a theme but get the following error page. It's not descriptive, but perhaps an error is logged by the server. New Bitmap Image.bmp
  23. That case looks very nice, and on the surface looks pretty easy to work with as far as ITX cases go. Your CPU and RAM sound on the level; the i5 should serve you well for emulation. I'm not familiar with radeon cards but that one seems nice. Hope you enjoy your foray into rig building and emulation. If you've not already chosen disk drives, I'd recommend a SSD for your main OS drive and mechanical drive for storing your roms. You could of course go all SSD if you want; prices have come way down in recent years.
×
×
  • Create New...