-
I've got a program, (http://rtool3.cjb.net) that's using the coolbar. It's nice and everything but a little research shows me it's the culprit of a, excuse my french, F**KING NASTY problem.
Im using VB6, VB5 doesn't introduce this, and it only happens in an executable. When Main() is running (including any functions that stem off it) and an error occurs, the program will give a runtime error, like it's supposed to. After main has finished (it's not structured so the program ends now), and an error occurs, it'll crash with a "Close...Details" type message box, but the bad thing is it causes an error in kernel32.dll, which as any geek knows, can really screw up your Windows session.
When running a program after the crash, it usually bluescreens and after about 2, you can't do much :) and are forced to reboot.
How am i sure it's the coolbar? I could be wrong, but i created a sample application that uses the coolbar. All it has is a button on it that has Err.Raise 5 in it. When i ran the binary, i hit the button and no error pops up, i just hear the sound that should be played from the runtime error box and the program just stops running. When i ganked the coolbar from my program, it crashes in msvbvm60.dll, which i think is at least better than the kernel.
Why do i think it's crashing? Knowing VB is an interpreted language, something probably fux0rs what ever is layered under it :)
Does anyone have any ideas? I like the coolbar, and id like to keep using it (partially because it keeps my interface clean :), except it makes debugging errors harder because
1) people hate it taking windows down
2) i dont understand the majority of the windows errors (runtime errors are just convenient :)
3) i lose code sometimes when windows crashes
------------------
-Mystiq
[This message has been edited by mystiq (edited 01-08-2000).]
-
-
I just read those pages, and i have more swears in my head then can be listed here. How stupid can they be to let that kind've error go by, do they not compile exes and test it before distributing?
Microsoft programmer's are defined by this joke:
How many Microsoft engineers does it take to change a light bulb?
Answer
None, they just redefine darkness as the new standard.
------------------
-Mystiq
