Livecode environment crashing when testing app
Posted: Wed Aug 29, 2012 10:13 pm
I am currently fiddling around with my first app in which i decided to try to read from one file in chunks and to write those chunks to another file until the EOF is reached. Thereby the file will be effectively copied over. Off course there are built-in functions for this but i want to extend this furter to be able to measure speeds, progress, limit speeds and to pause the copy so i need to have total control over the copy process.
The thing is however that when i switch to "live" mode (which is debugging i assume) and click the button which fires off my test the whole Livecode environment hangs (Windows white screen, not responding anymore when clicked). Off course i will probable have made a nasty bug (or two!) which reads past the EOF or something like that, but shouldn't i be able to debug this or at least terminate the debugging and try again? Now i must force close the whole Livecode environment and start it again.
So i'm not asking what i have coded wrong (which i know i have) but i would like to know if it is normal for this to happen or if i can avoid this? From my limited experience with other programming languages (Delphi, c#) i always had complete control in the debugger which is what you would also expect from a debugger.
Thanks
The thing is however that when i switch to "live" mode (which is debugging i assume) and click the button which fires off my test the whole Livecode environment hangs (Windows white screen, not responding anymore when clicked). Off course i will probable have made a nasty bug (or two!) which reads past the EOF or something like that, but shouldn't i be able to debug this or at least terminate the debugging and try again? Now i must force close the whole Livecode environment and start it again.
So i'm not asking what i have coded wrong (which i know i have) but i would like to know if it is normal for this to happen or if i can avoid this? From my limited experience with other programming languages (Delphi, c#) i always had complete control in the debugger which is what you would also expect from a debugger.
Thanks
