VB Bug, (Anyone got a good work-around ??)

[Paul282]

I'm sure you've all had this problem.

You're in a hurry, you quickly put together an idea and want to test an algorithm. just 10-15 lines of code or so, no interface because you just want to test the output to use in a proper app later.

You run it and find (for example) that an array was 1 based instead of zero based and your test goes into an infinite loop from the IDE.

Then, because VB can't recover you have to kill it and recode the F#$%*%G algorithm, because you were not writing a real app you didn't save it.

Just wondering if anyone has come up with any good work-around to this BUG in VB? a little function you could add in or something to allow a graceful exit.

(I hope the VB7 IDE can recover!, Borland C++ builder can, you just hit the stop button and it stops because it test the app in a different process to the IDE. VB IDE stalls and you can't hit the stop button)

????????????????????????????????????????????????

Paul

[Bad5887]

Just push 'alt+pause' that puts the program on 'break'.

[Juan Carlos Rey]

Wasn't it really Ctrl-Break???

[Zaf Khan]

I thought it was Ctrl + Break too, but sometimes the damn thing just ignores me.....

DocZaf
{;->

[joey o.]

Not that I'm stupid or even smart, I feel for you Paul282 'cause up untill a year ago I didn't know what the "break" button was. Every time I heard "Just press alt and break" I figured this was a thing I did not have 'cause all the letters were worn of my old used up keypad. When I broke down and spent the $12 for a new one, I found it in the very top row, last on the right. This has changed my life and I can loop all over hell now without a care!

[cwm]

sometimes when you're messing with api you have to press ctrl+breakyourgoddamnkeyboardoveryourcomputer...

[Tonio169]

When subclassing a control or a window, pressing ctrl+break sometimes doesn't work if the problem is within the window proc.

[Paul282]

WOW! Really, I'll try it later.

I always assumed that if the IDE interface hung then hot keys wouldn't respond either (not that I knew what they were anyway)

Thanks vbDoods

[Paul282]

It's Ctrl Break, Not Alt Break !!!
... and it works



AAAAAAAARRRRRRRRRRRRGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHH

Think of all that code I lost unnecessarily !!!!!!!!



Better still, don't

[Crazy D]

And to be safe, why not let VB save the project every time before you run it.. at least you never loose code.

Sometimes it takes some time (and a lot of ctrl+break's) to stop your program but most of the time it will stop.

Also you could add a doevents inside your loop so you can break it ez.

[Juan Carlos Rey]

Keep a good hammer by your keyboard...