Action Scripting A "Steeping Stone" - Really? Then why......

[SNusa]

Re: Action Scripting A "Steeping Stone" - Really? Then why......

Robert, I agree with Al. If I follow the steps you describe I see that you haven't left the Action Scripting editor. Instead if you're working with an "action" that consists of "inline" xbasic. Convert the whole script to xbasic from the Code menu, instead. There's no reason whatsoever to save your script to the code page to get to the Xbasic Explorer. You just have to convert the "script" to xbasic.... not the "action".

I must be missing something everyone.....

Action scripts that are assigned to button events on forms never even appear in the code tab in the first place. (even after conversion to inline X-basic)

I do realize that if you're working with converted action scripts that were originally created within the code tab, it's a different situation altogether.

However, if you're converting one particular in-line action scripts which requires modification (attached directly to a buttons action on a forms) this converted action script will never get to the code tab. (It's kept with the form, and thus the only place it is editable is from within the inline converted X-basic (modal) window that pops up when you right click on a button's event. (little window that zooms to larger one)

[SNusa]

Re: Action Scripting A "Steeping Stone" - Really? Then why......

I stand corrected on this. I keep my original on the button event, if necessary with an END in front of it. (when i have saved it as code.) thats the rollback version.
As was pointed out in a previousl post - if a form is lost, so are the form based scripts. I dont have first hand experience of this - thankfully.

A related potential problem here is no support for backing up "dropped" database items. Neither zipping or backing up includes these. Actually, I was about to post the related question of: What's the difference between backing up and zipping? (I can't seem to find much. ~ Anyone?)

I am truly surprised there is no backup/restore of previous version for items on the code tab.....
(Seems like a really important place for this kind of feature!)

In present configuration, I don't think there is any built in a5 backup tool which negates the need (and use) of third party zip/backup tools to grab the entire directory/subdirecty as a whole! ~ Especially since dropped tables are neither included in zips nor backups.

[Tom Cone Jr]

Re: Action Scripting A "Steeping Stone" - Really? Then why......

Yes, I think you're missing something. I have sent you a private message (through the message board), so check your messages here.

[SNusa]

Re: Action Scripting A "Steeping Stone" - Really? Then why......

Yes, I think you're missing something. I have sent you a private message (through the message board), so check your messages here.

Thank you Tom! (thinking about your tip, I came up with another option I like even better)

Also, I just found another workaround......
After disabling the action script (right click) attached to a button, right click and view X-basic code. (& copy code to clipboard using button)
Open a new tab on the code editor, paste code, save this script.
Add the action script (xbasic script) directly below the disabled script, to run X-basic code (now in Code tab) using script_play_local.

This option doesn't require leaving the code tab. It's quick and easy. (only a few mouse clicks) PLUS: You have now isolated this one script that needs modification, while leaving all the other action scripts still assigned to the objects event (Including the disabled source of this converted X-basic) "intact."

The best part of this is: At some later point, even if you convert all the action scripts attached to the objects action (into X-basic) nothing breaks. ~You end up with most of the X-basic still attached to the form, with a call to the isolated (original problematic x-basic code) on the code tab)....

And of course, you could (in theory) also further convert this X-basic code (on the code tab) into a function. (But to do so, you would probably have to pass some variables to this function using "byref" to "keep this train rolling.") Most certainly more work than it's worth.....