Jump to content
LaunchBox Community Forums

eatkinola

Members
  • Content Count

    797
  • Joined

  • Last visited

  • Days Won

    13

eatkinola last won the day on August 4 2019

eatkinola had the most liked content!

Community Reputation

617 Excellent

5 Followers

About eatkinola

  • Rank
    64-Bit Supercomputer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. That sucks man. I hope you are able to sort this all out soon so you can get back to your collection.
  2. @NRJMons, @retro6: Thanks for reporting the bug. This plugin has not worked since about LB version 10 when LB/BB was moved from .NET to .NET Core. There are some breaking changes there I've not yet sorted out. I've not had time to work on this in a while and have been very busy with work, so the plugin will not likely be fixed anytime soon.
  3. Please refer to the PDF config guide in the download.
  4. Thank you very much. I will take a look at it when I have a bit more time.
  5. Does WMP also look faded with other themes (that do not use my plugin)? Shouldn't ScrollSpeed be in quotes, i.e., ScrollSpeed="10"? Does it not work when speed is set to "1"? Your ScrollDelayBeg is 13.5 seconds, but I assume you're waiting that amount of time to see if anything appears.
  6. I don't think that's possible on the System view; I know of no trigger to determine when the Back option is selected. Well, I take that back -- it's probably possible if you can get at the list's data model and find out when "Back" is the selected item ... but that would be a bit hacky and would break with different languages. It's much easier to hide this on the Options menu (you likely had it working way before -- I did in Refaktor). If I can properly fix the resource leak with EnvironmentInfo, moving this info back to the Options view might be the best solution.
  7. Strange the view still works though it pops up these errors. I use VS 2019 to develop the plugin library, but I develop the themes outside of VS just using notepad. Interesting. I've never noticed that before, though I always run using WMP. Could it have to do with the codecs you use for WMP? I just use the default codecs bundled with Windows 10. I use this feature in most of my themes -- for example in Refaktor I set the speed to 3 and it works fine. How else is your marquee setup? I could take a look if you want to send some xaml I can test on my system.
  8. Yes, the lag will still be there as the classes used to grab environment info lag a bit on first load. It should not cause a lag in the UI thread since the environment info is grabbed on a separate thread. I get around this in MinimalX by using a fading animation so you cannot see the lag. UpdateContinuously False is recommended, as setting to True (which was the default prior to this release) leads to a resource leak; more threads are spawned which leads to about 5% extra CPU load on my system. I also recommend putting the environment info in System rather than Options (which I why I cha
  9. Do you also define aoc=".....Controls;assembly=...." at the top of the xaml? No, there should not be anything else you need to do. If you want to pm me your view/theme, I can take a look.
  10. With 3.9.7, you shouldn't need that Ignores... property, but if you still do let me know. 3.9.7 fixed a similar problem in MinimalX so I thought it'd also fix your theme. Thank you for clarifying. If we add an ellipsis to truncate the string, would it still need to scroll? Yes, that is correct. Resetting on each selection would be a workaround. I will have to try it; my initial concern is it would slowdown the list too much but would have to try it.
  11. UPDATED to v1.7
  12. UPDATED to v1.8
  13. As a workaround for the disappearing problem, try adding this property to the MarqueeTextBlock, works for me: IgnoreAutopauseListeners="True" I looked at the other "this" post. Would you please clarify what you mean by ellipsis (...)? Are you asking for ellipsis on the scroll text block even though it scrolls? EDIT: You can use the IgnoreAutopauseListeners workaround for now, but I did find a fix that will be in the updated library.
×
×
  • Create New...