91
3rd Party Plugins - (fb2k) / Re: JScript Panel
Last post by redorb -It is over and I am done.Thanks... not a day too soon.
It is over and I am done.Thanks... not a day too soon.
Thank you so much, hopefully it will be useful for others. Will also create a new repository just for my fork on github, so it will be a bit more "visible".
EDIT2: One of the things I don't like is that the your component overwrites the old component, which makes it very hard to test since you cannot compare the old and new component running side by side.You can absolutely compare the two versions running side-by-side on the x86 build. Just rename one component folder and DLL to something different. For example I renamed the old component <user components folder>/foo_vis_vu_meter/foo_vis_vu_meter.dll. Been running like that ever since I was able to decode the BIN format.VU Meter (DirectX12) CUI seems to have a one size fits all approach, compared to the old VU Meter.Settings are saved in 0.7.2. Just tested. I stared at the video for a long time trying to decipher what you're doing. Let me try to put it into words and note that what follows applies equally to DUI and CUI: you seem to have several instances running at the same time--more than 2. foobar2000 keeps the configuration in a SQLite database. So, I only hold 2 different sets of configuration settings at runtime because that is generally what fits in a single entry (unless I use blobs which was a pain in foo_vis_milk2 so decided to avoid that here). Basically ping-pong'ing between each new opened instance using the instance id modulo 2 to pick. Settings are then saved in the order of closing; last wins. But since "I think" you have more than 2 running at the same time, you might be saving one of the hidden windows depending on how foobar2000 is pumping the WM_DESTROY messages on exit. Fullscreen is special because in DUI it is associated with a non-fullscreen window which is a completely separate window from the embedded or undocked window which is a huge pain. Oh, and foobar2000 leaks memory when you create new panels; specifically in the settings/preferences data--it is in the proprietary player code--so don't go too crazy.
It also doesn't seem to save settings on exit as I have to set it up again every time I reboot fb2k. (I did not show this behavior in the video)
Surely I got something wrong in my interpretation of what's happening, but your use case is simply not something I envisioned. My setup is less visually impressive.
%APPDATA%\foobar2000-v2\foo_httpcontrol_data\foobar2000controller+ launch Foobar and setup appropriate settings in [see screenshot]:
File > Preferences > Tools > HTTP Control
http://192.168.1.240:8888/
Installed templates: foobar2000controller
git clone https://github.com/regorxxx/foobar2000-assets.git
Instance data is saved inside theme.fth for default UI.But just so no one claims I don't try to improve things, I just tried converting the configuration partially to it being per instance. Breaks fullscreen massively, due to the fullscreen implementation in Default UI where it is a completely separate instance. The breakage is unacceptable: I can't even exit fullscreen via regular methods, none of the BIN files transfer, the panel is not in the same mode, position, layout as the windowed version.
If you're using cfg_XXX or the configStore APIs inside these then you've seriously fucked up.