|
Post by johnmb on Apr 29, 2008 18:41:25 GMT -5
If I don't use RunBASIC it does a timeout after a specified period of time. I understand that: what I have trouble with is not knowing it has done a timeout and keying in some new code only then being told time had expired. When I return to the edit screen it is has been cleared! Can it be changed so that a user is notified at the edit screen before or as code is being keyed?
John
|
|
|
Post by Janet on Apr 29, 2008 20:05:39 GMT -5
I think you can change it in your preferences, John. Did you try backpaging your browser instead of clicking the edit link? That usually works for me. Then I do a quick copy and paste of the code. Mostly I can then save and continue, but, at least I have a copy of the code if I really am locked out.
|
|
|
Post by johnmb on Apr 29, 2008 20:27:58 GMT -5
The key is knowing before you keyin and execute your code that the timeout has occurred. After the attempt to execute you get the message of the elapsed timeout. Are you saying that at this point I should use the browser 'back arrow' and my code will still be in the edit window? Will I also be younger? The back button has not done that in the past for me that I know of. I am willing to share with you this amazing new discovery.
If so I will try it.. Setting a different time interval won't help me: I would just wait a little longer at times before I went back to RunBASIC.
Thank you, John
|
|
|
Post by Jerry Muelver on Apr 29, 2008 21:22:35 GMT -5
In any browser interface to action (except JavaScript-driven links), the Back button is your friend. It's saved me many a time, in forum message-typing, email-answering, forms-filling-out, and, yes, RB programming. Experiment with it, to find out the capabilities. It's a kindred spirit with Google's "Cache" version of long-gone pages, and the marvelous Way Back Machine at archive.org.
|
|