new version (0.0.3) of foo_tunes available
download here
Full Version: new version (0.0.3) of foo_tunes available
Should it work in win98?
stripe/ben
stripe/ben
no, this runs on windows2000 and windowsXP (only)
Drat.
ben/stripe
ben/stripe
QUOTE(ne_me_sis @ Nov 19 2003, 11:08 AM)
no, this runs on windows2000 and windowsXP (only)
Correction: it runs on Windows 2000, Windows XP and later (Windows Server 2003 for example).
Bug:
total wrong Explorer Trees
total wrong Explorer Trees
Still crashes with foo_looks. Any idea what is causing this yet ?
QUOTE(Gord @ Nov 19 2003, 08:33 PM)
Still crashes with foo_looks. Any idea what is causing this yet ?
I tested it in my debugger, so the crash is inside foo_looks.dll. Please ask author of foo_looks for tests with foo_tunes.
DanZ (the developer of foo_looks) said:
Maybe you two must try to solve the problem together...
QUOTE
I've tried debugging this on my side and don't know what's going wrong. I was hoping you might try it when debugging your code?
Maybe you two must try to solve the problem together...
You shouldn't be using foo looks and foo tunes. Since they are both to replace the ui use just one or the other. If they are causing problems it's not even worth investigating since you can't use both.
QUOTE(ne_me_sis @ Nov 19 2003, 11:03 PM)
QUOTE(Gord @ Nov 19 2003, 08:33 PM)
Still crashes with foo_looks. Any idea what is causing this yet ?
I tested it in my debugger, so the crash is inside foo_looks.dll. Please ask author of foo_looks for tests with foo_tunes.
It's odd as foo_looks works with foo_ui_light. I'll ask danZ anyway.
QUOTE(radfaraf @ Nov 21 2003, 04:32 AM)
You shouldn't be using foo looks and foo tunes. Since they are both to replace the ui use just one or the other. If they are causing problems it's not even worth investigating since you can't use both.
Actually foo_looks is not there to replace the standard UI. It's more like an addition for it.
QUOTE(danZ @ Nov 20 2003, 07:59 PM)
I posted in his thread that I can't get any good debugging info on my side. I tried foo_tunes, I see the crash, but I don't get any good information. I could be wrong but I think the problem is on his side somehow but I don't have a clue as to what it might be.
Pass the buck back to Mr. ne_me_sis
PS. Is there a way to turn off the failure.txt stuff and actually let the thing crash? Maybe then I'd get more information.
Pass the buck back to Mr. ne_me_sis
PS. Is there a way to turn off the failure.txt stuff and actually let the thing crash? Maybe then I'd get more information.
danZ doesn't seem to be able to figure it out either. Kinda sucks. Guess I'll just stick with the default UI until they either work together or something else comes along.
For whatever reason, all keystrokes are passed to foobar as hot keys, even when typing in a dialog (like a file save dialog, or the database search box).
This is terribly annoying i hate to say.
It doesnt happen with default user interface either, so it is definitely an issue with foo_tunes.
Hope this gets fixed... when it does, I will probably use foo_tunes 24/7.
Great work so far though.
-foo_tunes 0.3
-foobar 0.7.4 beta 2
This is terribly annoying i hate to say.
It doesnt happen with default user interface either, so it is definitely an issue with foo_tunes.
Hope this gets fixed... when it does, I will probably use foo_tunes 24/7.
Great work so far though.
-foo_tunes 0.3
-foobar 0.7.4 beta 2
Hello ne_me_sis,
Sorry for questionning but... any update of your brilliant GUI ? Do you plan to support playlist font and color ?
I like it so much
Sorry for questionning but... any update of your brilliant GUI ? Do you plan to support playlist font and color ?
I like it so much
QUOTE(Gord @ Nov 21 2003, 04:13 AM)
QUOTE(danZ @ Nov 20 2003, 07:59 PM)
I posted in his thread that I can't get any good debugging info on my side. I tried foo_tunes, I see the crash, but I don't get any good information. I could be wrong but I think the problem is on his side somehow but I don't have a clue as to what it might be.
Pass the buck back to Mr. ne_me_sis
PS. Is there a way to turn off the failure.txt stuff and actually let the thing crash? Maybe then I'd get more information.
Pass the buck back to Mr. ne_me_sis
PS. Is there a way to turn off the failure.txt stuff and actually let the thing crash? Maybe then I'd get more information.
danZ doesn't seem to be able to figure it out either. Kinda sucks. Guess I'll just stick with the default UI until they either work together or something else comes along.
I'll take another look when I ready to release foo_looks 2.0.
I love this interface. A couple of bugs though. Whenever I try to do right click explorer things in the explorer window (copy, paste, search, rename...etc) it usually crashes. For example, here is a crash I just got while making a search :
For this crash, I made a right click search for *.jpgs, closed the search window, and then went back to foobar. It crashed immediately. Again, I love this interface, and look forward to a more stable release.
CODE
Illegal operation:
Code: C0000005h, flags: 00000000h, address: 71763E9Eh
Access violation, operation: read, address: 3F6493DFh
Call path:
WinMain=>app_mainloop
This is the first crash logged by this instance.
Code bytes (71763E9Eh):
71763E5Eh: C0 5F 5E 5B C9 C2 08 00 8B 44 24 04 56 8B 48 28
71763E6Eh: 8B 44 24 0C 3B C1 75 0C 8B 41 08 85 C0 74 12 66
71763E7Eh: 83 60 1C 00 66 8B 70 20 66 03 70 1C 66 85 F6 77
71763E8Eh: 05 83 C8 FF EB 19 50 E8 7A EB FE FF 85 C0 74 0C
71763E9Eh: 66 8B 48 20 66 89 70 1C 03 F1 EB EA 0F B7 C6 5E
71763EAEh: C2 08 00 8B 44 24 04 56 57 33 FF 8B 70 08 85 F6
71763EBEh: 74 1F 0F B7 46 20 03 F8 83 7E 08 00 74 0E F6 46
71763ECEh: 14 20 74 08 56 E8 D9 FF FF FF 03 F8 8B 76 04 EB
Stack (0012F3FCh):
0012F3DCh: F4 64 FB 77 70 16 F8 77 FF FF FF FF 9C D4 F8 00
0012F3ECh: 73 F5 59 7C 00 00 07 00 00 00 00 00 20 C1 BD 08
0012F3FCh: C0 FC 15 00 30 2E 75 71 C0 FC 15 00 D0 FD 15 00
0012F40Ch: C0 FC 15 00 FA 50 75 71 C0 FC 15 00 01 00 00 00
0012F41Ch: 0B 00 00 00 25 50 75 71 01 00 00 00 A6 B7 FC 77
0012F42Ch: 0A 00 00 00 58 8F 15 00 00 00 13 00 B8 8A 15 00
0012F43Ch: 00 00 00 00 00 00 13 00 00 00 13 00 78 01 13 00
0012F44Ch: C0 98 FC 77 08 06 13 00 46 98 FC 77 78 F4 12 00
0012F45Ch: D0 A2 E3 77 9E 02 4B 00 0B 00 00 00 01 00 00 00
0012F46Ch: 00 00 00 00 25 50 75 71 CD AB BA DC 9C F4 12 00
0012F47Ch: 21 6B E1 77 25 50 75 71 9E 02 4B 00 0B 00 00 00
0012F48Ch: 01 00 00 00 00 00 00 00 18 F6 12 00 0C DC 12 06
0012F49Ch: BC F4 12 00 10 50 E2 77 25 50 75 71 9E 02 4B 00
0012F4ACh: 0B 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
0012F4BCh: 00 F5 12 00 30 DC 89 01 25 50 75 71 9E 02 4B 00
0012F4CCh: 0B 00 00 00 01 00 00 00 00 00 00 00 00 00 00 C0
0012F4DCh: 0B 00 00 00 80 83 50 00 9E 02 4B 00 0B 00 00 00
0012F4ECh: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0012F4FCh: 00 00 00 00 20 F5 12 00 D0 A2 E3 77 0C DC 12 06
0012F50Ch: 0B 00 00 00 01 00 00 00 00 00 00 00 0B 00 00 00
Registers:
EAX: 3F6493BF, EBX: 0000000B, ECX: 001A0F60, EDX: 00002101
ESI: 02846A9C, EDI: 00000200, EBP: 0012F458, ESP: 0012F3FC
Failed to get module/symbol info.
Version info:
foobar2000 v0.7.6 beta 1
UNICODE
Code: C0000005h, flags: 00000000h, address: 71763E9Eh
Access violation, operation: read, address: 3F6493DFh
Call path:
WinMain=>app_mainloop
This is the first crash logged by this instance.
Code bytes (71763E9Eh):
71763E5Eh: C0 5F 5E 5B C9 C2 08 00 8B 44 24 04 56 8B 48 28
71763E6Eh: 8B 44 24 0C 3B C1 75 0C 8B 41 08 85 C0 74 12 66
71763E7Eh: 83 60 1C 00 66 8B 70 20 66 03 70 1C 66 85 F6 77
71763E8Eh: 05 83 C8 FF EB 19 50 E8 7A EB FE FF 85 C0 74 0C
71763E9Eh: 66 8B 48 20 66 89 70 1C 03 F1 EB EA 0F B7 C6 5E
71763EAEh: C2 08 00 8B 44 24 04 56 57 33 FF 8B 70 08 85 F6
71763EBEh: 74 1F 0F B7 46 20 03 F8 83 7E 08 00 74 0E F6 46
71763ECEh: 14 20 74 08 56 E8 D9 FF FF FF 03 F8 8B 76 04 EB
Stack (0012F3FCh):
0012F3DCh: F4 64 FB 77 70 16 F8 77 FF FF FF FF 9C D4 F8 00
0012F3ECh: 73 F5 59 7C 00 00 07 00 00 00 00 00 20 C1 BD 08
0012F3FCh: C0 FC 15 00 30 2E 75 71 C0 FC 15 00 D0 FD 15 00
0012F40Ch: C0 FC 15 00 FA 50 75 71 C0 FC 15 00 01 00 00 00
0012F41Ch: 0B 00 00 00 25 50 75 71 01 00 00 00 A6 B7 FC 77
0012F42Ch: 0A 00 00 00 58 8F 15 00 00 00 13 00 B8 8A 15 00
0012F43Ch: 00 00 00 00 00 00 13 00 00 00 13 00 78 01 13 00
0012F44Ch: C0 98 FC 77 08 06 13 00 46 98 FC 77 78 F4 12 00
0012F45Ch: D0 A2 E3 77 9E 02 4B 00 0B 00 00 00 01 00 00 00
0012F46Ch: 00 00 00 00 25 50 75 71 CD AB BA DC 9C F4 12 00
0012F47Ch: 21 6B E1 77 25 50 75 71 9E 02 4B 00 0B 00 00 00
0012F48Ch: 01 00 00 00 00 00 00 00 18 F6 12 00 0C DC 12 06
0012F49Ch: BC F4 12 00 10 50 E2 77 25 50 75 71 9E 02 4B 00
0012F4ACh: 0B 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00
0012F4BCh: 00 F5 12 00 30 DC 89 01 25 50 75 71 9E 02 4B 00
0012F4CCh: 0B 00 00 00 01 00 00 00 00 00 00 00 00 00 00 C0
0012F4DCh: 0B 00 00 00 80 83 50 00 9E 02 4B 00 0B 00 00 00
0012F4ECh: 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0012F4FCh: 00 00 00 00 20 F5 12 00 D0 A2 E3 77 0C DC 12 06
0012F50Ch: 0B 00 00 00 01 00 00 00 00 00 00 00 0B 00 00 00
Registers:
EAX: 3F6493BF, EBX: 0000000B, ECX: 001A0F60, EDX: 00002101
ESI: 02846A9C, EDI: 00000200, EBP: 0012F458, ESP: 0012F3FC
Failed to get module/symbol info.
Version info:
foobar2000 v0.7.6 beta 1
UNICODE
For this crash, I made a right click search for *.jpgs, closed the search window, and then went back to foobar. It crashed immediately. Again, I love this interface, and look forward to a more stable release.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.