Post by rich357 on Dec 13, 2009 23:44:01 GMT -5
www.qrz.com/xtest2.html
I have become quite disillusioned with Run Basic in the past few weeks. As I have been trying various methods to duplicate the flash version of the test at the above site, into a RunBasic version, I just do not see how it can be done.
Specially not the way I want. When I try one method, something in your scheme of things causes the program to hang. When you employ a button or link, the wait statement can cause havoc simply because it is not in the exact place it should be in.
As I see it, wait, should be something similar to "onClick". But no, having a "wait" inside of a loop, causes the output of that loop to halt. here's a quick example.
Of course, if "wait" is after "next", then I get the 10 buttons as desired.
In my latest version of the test, I have written two functions which show two different tables. If I put the "wait" anywhere other than within the function, the program hangs.
I think we should have some better way of dealing with buttons and links. As it is now, onclick gives us the choice of a branch label or a sub routine. But that has it's drawbacks as well. The wrong placement of a branch label and the program hangs or an error message pops up and says "branch label not found".
Now you may be thinking by now that I'm giving up the ship.
Hardly. As the man once said, "I've only just begun to fight!".
As I've got nothing else better to do to keep me busy, I just may yet find a way to make this blasted test work MY WAY!
I have become quite disillusioned with Run Basic in the past few weeks. As I have been trying various methods to duplicate the flash version of the test at the above site, into a RunBasic version, I just do not see how it can be done.
Specially not the way I want. When I try one method, something in your scheme of things causes the program to hang. When you employ a button or link, the wait statement can cause havoc simply because it is not in the exact place it should be in.
As I see it, wait, should be something similar to "onClick". But no, having a "wait" inside of a loop, causes the output of that loop to halt. here's a quick example.
for n=1 to 10
button #a,"a",[quit]
wait
next n
[quit]
end
Of course, if "wait" is after "next", then I get the 10 buttons as desired.
In my latest version of the test, I have written two functions which show two different tables. If I put the "wait" anywhere other than within the function, the program hangs.
I think we should have some better way of dealing with buttons and links. As it is now, onclick gives us the choice of a branch label or a sub routine. But that has it's drawbacks as well. The wrong placement of a branch label and the program hangs or an error message pops up and says "branch label not found".
Now you may be thinking by now that I'm giving up the ship.
Hardly. As the man once said, "I've only just begun to fight!".
As I've got nothing else better to do to keep me busy, I just may yet find a way to make this blasted test work MY WAY!