Could one of you people that have the frontend settings trouble export a theme file (assuming you use the Default UI)?That is, coincidentally, the sane way of preserving any settings.
Quote from: NullString on 08 March, 2012, 09:07:13 PMI had a problem regarding a "Nothing happens when I click Frontend settings", even though I had all the prerequisites installed. The problem got solved when I deleted the UI element, and added it again with the default settings. Now I can edit the frontend settings. =)Whoa, I somehow missed this post.Does this preserve the settings in use before the element was removed?I don't really have to change anything right now, as it's set up how I want it, but I don't believe I have any way of copying the settings somewhere before replacing the element.
I had a problem regarding a "Nothing happens when I click Frontend settings", even though I had all the prerequisites installed. The problem got solved when I deleted the UI element, and added it again with the default settings. Now I can edit the frontend settings. =)
FYI for your future configuration needs, there is nothing inherent about simple playlist view that does not allow full customization. You were using a layout with only one panel filled with the playlist. No place to add something without replacing what was there. What you would do to add a panel is temp replace the playlist with a splitter of your choice which would then give you multiple locations to add panels. Then add back the playlist in one panel and your seekbar in another.
Add it as a panel, not a toolbar element, then you can resize it to however you like.
I accidentally put the screenshot functionality in the latest (0.2.21) build as I rushed it out to fix a resume-from-hibernate/sleep crash.The screenshot functionality is controlled via advanced preferences.There's a size setting and a titleformat string for naming the file.If the path is just a filename, it ends up as a PNG in My Pictures.If it's a full path, it probably ends up in that location with that name.This functionality only works with the Direct3D9 frontend, as I haven't been arsed to implement it for the other ones. Expect it to be unstable.
It seems to work fine.
Ah my problem was that for some reason all of the files weren't being read in correctly so I re-downloaded and copy pasted them back into the components folder and restarted foobar. It now recognizes a difference between the GDI, direct3 9 and the direct2before, it was just rerouting to the GDI
For me, it always exports the same waveform, although I wanted to export another waveform. It simply generates another PNG with the Name of the target waveform but with the image of an earlier waveform.