Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: pre-0.38 test (Read 7227 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

pre-0.38 test

http://foobar2000.hydrogenaudio.org/pre-0.38.rar
people have been asking for a seeking bar so heres one (in foo_ui_classic.dll)
foo_ui_classic is still halfdone, you might want to remove it.
0.36/0.37 inputs still work
Microsoft Windows: We can't script here, this is bat country.

pre-0.38 test

Reply #1 –
Don't want to alarm you, but the current version was the first to ever give me a crash! On exit, in foobar2000.exe. can't reproduce, but have xp drwtsn32.log.
.

pre-0.38 test

Reply #2 –
you sure you didn't have any weird "third-party" dlls in the directory when that happened ? did it you have foo_ui_classic loaded ?
[edit] PM me if you want to email/uplad the log, i'll give you info
Microsoft Windows: We can't script here, this is bat country.

pre-0.38 test

Reply #3 –
no third party dlls - but it wasn't installed to a clean dirctory. foo_classic_ui not loaded, ive pm'd you.
.

pre-0.38 test

Reply #4 –
Sweeeeeet

pre-0.38 test

Reply #5 –
It would be nice if I could drop a file on the UI and have it load...

pre-0.38 test

Reply #6 –
ok, thanks, i'm looking into the log now.
Microsoft Windows: We can't script here, this is bat country.

pre-0.38 test

Reply #7 –
ok, i believe i've fixed it, file updated.
thanks for the log again, it would take a while for me to encounter/figure it without those numbers.
Microsoft Windows: We can't script here, this is bat country.

pre-0.38 test

Reply #8 –
Is the new UI supposed to be a template for where people can replace the buttons?

I actually believe it looks less professional and more of just a hack, why not take X-Fixer's idea and place the buttons in the same region as he did?

Also with the slider, why make it a separate form? How about just placing the slider at the bottom of the program. Who wants to separate windows open when they are using foobar! Right under the playlist would be the best ption in my opinion.

These are opinion based views, but I bet others will probably feel the same way!

pre-0.38 test

Reply #9 –
read my first post again
Quote
foo_ui_classic is still halfdone

and yes, this is intended to be a "hello world" UI replacement component.
Microsoft Windows: We can't script here, this is bat country.

pre-0.38 test

Reply #10 –
OK, seems good, because it was happeing fairly regulary with that version but is fine now 

But on a minor note, if I forward past the end of a song by holding right (have to hold) with remaining time on, it will sometimes show a wierd number (the 0:496 one) in the time part on the status bar for a fraction of a second.

And also, I noticed you changed the forwarding past end of song thing (ok maybe not), but it is buggy. Open foobar, play and hold right key. Sometimes it willl stop at the end of the current song, sometimes it will continue for a few songs then stop. And on pressing play again, it shows that 0:4967 number again for a fraction of a second.

But I can live with all of that

Thanks again..
.

pre-0.38 test

Reply #11 –
Classic UI position is not saved (even if option is turned on in prefs).
But, nice work

pre-0.38 test

Reply #12 –
Who need classic UI. Forget all that UI cr..p.  Concentrate on the optimized code that this prog was designed for. After all modules codes were debugged and strategically positioned to reflect the musical algorithms of the sound waves, then, only then, you should worry about the look!. Period! (w00t)

pre-0.38 test

Reply #13 –
"classic ui" component is needed at least as samplecode (to demonstrate how to do such things in a legal way, to prevent foo_butt.dll SNAFU from repeating itself), someone else can take it and make it look pretty when 0.38 is done (not that i'm ever going to use it myself).
also, i need it to test API interface, i left major flaws in playback control API in 0.36 due to lack of any testing on my side.
Microsoft Windows: We can't script here, this is bat country.

pre-0.38 test

Reply #14 –
uh how do i disable these buttons in 0.38 ?

pre-0.38 test

Reply #15 –
An option for placing the buttons under the normal menu would be nice, to have them correctly in two seperated lines when you use a small window size.

pre-0.38 test

Reply #16 –
Quote
uh how do i disable these buttons in 0.38 ?

delelete foo_ui_classic.dll

pre-0.38 test

Reply #17 –
Quote
delelete foo_ui_classic.dll


no such file in the directory

pre-0.38 test

Reply #18 –
Oh, I see the... menus. The classic UI component just pops up a second UI window, complete with seek bar.

Oh, and I win an award for the stupid typo.

pre-0.38 test

Reply #19 –
Quote
Quote
delelete foo_ui_classic.dll


no such file in the directory

make sure u have enabled "show all files" and unchecked "hide system files" in the  "folder options - View"

pre-0.38 test

Reply #20 –
Quote
Oh, I see the... menus. The classic UI component just pops up a second UI window, complete with seek bar.

Oh, and I win an award for the stupid typo.

Quote
Oh, I see the... menus. The classic UI component just pops up a second UI window, complete with seek bar.


so they're here for good ?

Quote
Oh, and I win an award for the stupid typo.


heehee no problem there

pre-0.38 test

Reply #21 –
the installer exe of fb2k .38 test doesn't come with foo_ui_classic.dll, or mine didn't at least
But the pre-0.38.rar does
But you can just do a simple copy and paste

uh-huh

pre-0.38 test

Reply #22 –
Quote
to prevent foo_butt.dll SNAFU from repeating itself

peter, stop that, please. you're talking like no of your own programs has ever crashed (and do I hear how bad hacks are from the person who've just tried to hack-fix his program?)

also, subclassing is legal and is used everywhere in Windows. and it's required if you don't want to create new windows (or until you'll simply GIVE ME UI CODE, or really separate UI from core). and it will not cause any "problems" unless you'll start changing IDs. anyway it's my problem, not yours. and if you don't like/need plug-in, just do not install it. that's what the whole "components system" is about.

btw, 0.38 has a new bug - on startup it reports both PLAYBACK_IS_PLAYING and PLAYBACK_IS_PAUSED being ON (while they're obviously off). 0.37 worked fine.
 

pre-0.38 test

Reply #23 –
X-Fixer, aren't you getting the message yet ? you are a troll and an irresponsible piece of shit (making code that crashes when run under different version of fb2k, then blaming me for the mess you did, especially that i broke the component compatibility to get features YOU requested to work), you and your code are no longer welcome here.
perhaps Nullsoft tolerated hacks in "plugins" having random conflicts with any change in the exe, but i'm going to fight everyone who does so in fb2k, to prevent fb2k from going the way of winamp2.
i'm not going to involve myself into your childish discussion about window subclassing; fb2k is going to have formal interfaces for all things you would want to do with subclassing, you have a problem with waiting a few days/weeks before those things are finished.
as for "talking like none of my executables ever crashed" - it's a matter of being able to take the responsibility for your code. other developers i'm cooperating with make mistakes too, but they don't try to blame anyone else for that, and post fixes as soon as only possible. everyone makes mistakes, but you can't handle your ones.
Microsoft Windows: We can't script here, this is bat country.