QUOTE(cRoMo @ Apr 29 2006, 03:20 PM)

QUOTE
Wine is meant to emulate Windows. So if it doesn't happen on Windows, you are right I won't be very interested.
...
2. If you ran Wine in a Terminal you would have seen it is caused by RealChildWindowFromPoint not being implemented in Wine.
Firstable, to be clear - wine is not an emulator.
Well I consider it an emulator. From wikipedia: "A software emulator allows computer programs to run on a platform (computer architecture and/or operating system) other than the one for which they were originally written." You may disagree, I don't think its particulary important anyway.
QUOTE(cRoMo @ Apr 29 2006, 03:20 PM)

It works as a complete API rewrite, i.e. more less it's like you are running foobar on some other unique version of Windows, rather that under an emulator.
Right.
QUOTE(cRoMo @ Apr 29 2006, 03:20 PM)

Secondly - as I said, it's not the wine bug itself, i.e. wine quits clearly without eny errors. It's the foobar that reports bug.
There are plenty of ways it could crash in my code and be Wine's fault. "It doesn't prove anything."
QUOTE(cRoMo @ Apr 29 2006, 03:20 PM)

I am always running wine from console to see its messages and/or errors. Again, there are no wine errors at all when foobar crashes.
I though you will be interested in fixing this bug anyway, since a bug is a bug, at least in my opinion.
Well I am telling you 100% second crash is from unimplemented RealChildWindowFromPoint. If you look at the second crash you can see some odd exception code. Do you know what that exception code is? I don't. My guess: Wine specific. And when I run Wine from terminal I get the second crash too. Accompanied by a message in the terminal saying something about "unimplemented user32!RealChildWindowFromPoint called ... aborting ... passing to debugger". So there you go.
QUOTE(cRoMo @ Apr 29 2006, 03:20 PM)

QUOTE
3. Audio latency - Well Wine is an emulator.
But how comes under default UI I won't experience any latency? That's why I assume this is somehow ui_columns fault.
By the same logic: It doesn't happen under Windows, so its Wine's fault.
If I had to guess, I would say its maybe caused by the visualisation. The Columns UI one runs at a higher framerate. And the rendering code is probably quite different and maybe turns out slow on Wine. Plus default UI stops updating when minimised.
QUOTE(cRoMo @ Apr 29 2006, 03:20 PM)

QUOTE
1. Crash when mouse over playlist switcher panel I "fixed" on my side already. But it doesn't excuse Wine.
As I said, it's not wine that crashes, it's foobar. I know your point that this bug won't appear under stock windows, but again, it's the ui_columns that crashes, not wine.
Yes, but I explained that above.
I just found a message and patch about the specific problem here in Wine:
http://www.winehq.org/pipermail/wine-patch...ary/023772.html[edit]Here is some reference for the other problem:
message,
reply