61
General Discussion / Re: How To Recover Off-Screen Modules
« on: June 01, 2021, 06:31:41 PM »
anyone else?
Latest restricted WACUP beta release is build #19100 (May 10th 2024) (x86 & x64 changelogs) | Latest WACUP public preview is build #19100 (May 10th 2024) (x86 only)
NOTE: Beta testers are added in a limited & subjective manner as I can only support so many people as part of the beta test program to keep it useful for my needs.
Unless I think you're going to be helpful, not all requests will be accepted but might still be later on. Remember that beta testing is to help me & the limitations currently works for my needs for this project.
Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
62
General Discussion / Re: How To Recover Off-Screen Modules
« on: May 29, 2021, 09:28:33 PM »What windows are missing ?missing :
-dro
WACUP (main?)
Classic Spectrum Analyzer
Playlist Editor
Equalizer
Waveform Seeker
NOT missing :
Big Clock (lucky)
Album Art (probably because its size is +75% of the full monitor
63
General Discussion / Re: How To Recover Off-Screen Modules
« on: May 29, 2021, 08:21:07 PM »From the command-line wacup.exe /RESETCLASSICSKINPOSno joy
That should work for anything that's officially known about. For 3rd party plug-ins then it's manually editing config files which would need to be added to the known list of values to be handled.
-dro
64
General Discussion / How To Recover Off-Screen Modules
« on: May 29, 2021, 05:41:18 PM »
While playing around with the app sizing feature (Classic 2 x) several modules have vanished! Actually, my guess is that they are simply out-of-view of the desktop and am clueless how to drag them back into view. I hope there is a way without resorting to a system recovery or re-install. -thx
66
Preview Build Discussion / Re: Classic (2x) Observation
« on: April 30, 2021, 11:16:28 PM »CTRL + D or the D in the small clutterbar, next to the small visualizer area of the main windowNo EFFING way!!!!! Where in the EF is this stuff documented?!?!?!? When I clik WACUP Help of F1 Scotty beams me to this website. OK, but what if no interenet?
?-thx!
67
Preview Build Discussion / Re: Classic (2x) Observation
« on: April 30, 2021, 09:53:54 PM »
^
good reply - now, if someone can show me how to get my 1x skin back, thx.
good reply - now, if someone can show me how to get my 1x skin back, thx.
68
Preview Build Discussion / Classic (2x) Observation
« on: April 29, 2021, 11:25:44 PM »
With the new build I am trying out the larger interface. I notice that all features are indeed twice the size. However, the text size in the main playlist editor area (where the tracks are listed) is not changed. I was going to double-check this before I post, but I have not been able to discover how to set it back to 1x.
69
Wishlist / Feature Requests / Re: New Classic Skin Size
« on: March 26, 2021, 12:53:36 AM »thx Darren. Hope we both live long enough to see this realized. Myself? Well, I have been walkin' the planet long enough as to have been in a local band playing covers of Cream, Hendrix, Yardbirds when their music was current. I am a stone-age dinosaur, closer to The End than the Beginnings (heh heh, yeah - we played those tunes (Doors/CTA) also ... (hope you be much younger).
70
Wishlist / Feature Requests / New Classic Skin Size
« on: March 25, 2021, 11:46:56 PM »
I am giving the Main Menu > Options > Double Size a try. I like it, kinda. Would like to see a size half way between original and double. Will walk the plank here and go one further with a request for incremental options between original and double.
71
Preview Build Discussion / Re: Media Library History Anomaly?
« on: March 24, 2021, 11:24:35 PM »... One option is to enable the option to wait for a few seconds for it to track.option resolves issue - thx!
-dro
72
Preview Build Discussion / Media Library History Anomaly?
« on: March 24, 2021, 08:30:48 PM »
Judging from my Media Library History the playback logging of my pc's folders and files are not present. Only my bookmark playback (internet stations) are present in the history window. I am concluding it is this build, as the dates coincide with the build release. I have played literally hundreds of files/folders since the release.
Hoping it's just me pushing the wrong buttons. I say this because of the strange presence of the 'Tears of Magdalena' track.
Hoping it's just me pushing the wrong buttons. I say this because of the strange presence of the 'Tears of Magdalena' track.
73
Preview Build Discussion / Re: File access not possible after pressed stop
« on: March 21, 2021, 08:40:56 PM »
^
this issue does not seem to be a wacup defect. as you say, winamp does not have this issue, only dro can validate it a bug or not. there are winamp behavior (not many, but few) that does not apply to wacup.
if not a bug, perhaps it moves into the enhancement request forum. i am curious to know what percentage of the wacup community consider this an issue. imo, little-to-nobody, based on lack of any other users contributing to this topic (thus far). Perhaps there is a great deal of this issue being reported in the beta forum, of which we 'commoners' can have no knowledge of.
this issue does not seem to be a wacup defect. as you say, winamp does not have this issue, only dro can validate it a bug or not. there are winamp behavior (not many, but few) that does not apply to wacup.
if not a bug, perhaps it moves into the enhancement request forum. i am curious to know what percentage of the wacup community consider this an issue. imo, little-to-nobody, based on lack of any other users contributing to this topic (thus far). Perhaps there is a great deal of this issue being reported in the beta forum, of which we 'commoners' can have no knowledge of.
74
Preview Build Discussion / Re: File access not possible after pressed stop
« on: March 21, 2021, 05:40:50 PM »I am on Windows 10. Following your example, yes, a 'New Text Document.txt' is created. Once opened for editing you can delete the file 'New Text Document.txt'. Howvever, the open document remains. Nothing accomplished. Back to topic, answer my previous question : How is this an issue?The file is open/locked in the 'stop' condition and should not be able to delete. As it should be. If you must delete with the app still running simply load/play a new file. How is this an issue?Maybe you are going completely wrong here because this is not true. Let me give you another example for Windows. Create a txt-File, open it with the editor and try to delete - it works.
75
Preview Build Discussion / Re: File access not possible after pressed stop
« on: March 20, 2021, 09:57:58 PM »... Play a file, press stop and try to delete it.The file is open/locked in the 'stop' condition and should not be able to delete. As it should be. If you must delete with the app still running simply load/play a new file. How is this an issue?