Problem with scripts that require file browsers

Try commenting out the "fillin" in the script, add a "#" to the beginning of the line. Without a fillin value provided, the "Save As" will wait for input. (At least it did for my test!)

Thanks,

I'm not quite understanding how this would help during a -nographic script run though.
It's not interactive at all.

The issue seems to be that I need to be able to "setwindow" to the browser window, and know
what the FORM name is.  Using the record and replay functionality, there isn't anything there.
I'm seeing a generic "setwindow text" which doesn't work at all.

Still looking for hints.  Below script doesn't work. It just leaves the File Browser empty and hanging.
This is a literal Record session.

Any other suggestions are GREATLY APPRECIATED!

Thanks All, -Mike 

-----------------------------------------------------------------------------------------

setwindow pcb

trapsize 1876380

generaledit

netin 

setwindow form.niparams

FORM niparams import  

setwindow pcb

setwindow text

save

fillin "MIKEtest.txt"

setwindow text

close

setwindow form.niparams

FORM niparams cancel  

setwindow pcb

generaledit  

-------------------------------------------------------------------------------------------------------- 

OK, "nograph(ic)" is not interactive at all. IF I run script in interactive mode, having no "fillin" value for the "save" / "save as" waits for a value for the filename to save, with a "fillin" the file gets saved as that name and the script completes - "replay <script_file>" at the command window. Maybe this was changed at some point, which exact version are you running?

I'm running Allegro 16.6 for windows.

If you've got a script you could post or send that handles those browser windows properly,
I would really appreciate it.

Thanks oldmouldy.

 -Mike 

First off, you will only be able to use the "save", or "saveas" in interactive mode. When you use "something like" "save" or "saveas" the "fillin" step puts the value in the browser window and closes it, so it will then "always" save(as) to the same filename. If you don't have a "fillin value" step the "save" / "saveas" will wait for user input for thje filename. If you want to have a script that changes the "fillin value" based upon "some other variable when it runs", you will need to take a look at the SKILL forum, there was recently a post from eDave where he had a SKILL script that wrote an Allegro script and then replayed that from the SKILL script. I would post the link but this post would be moderated as a result.