IconX, Ask and Workbench 1.3

[Gilloo]

Got this little script shell named test

echo "Hello world"
ask "continue ?"
if WARN
echo "you are OK to continue"
else
echo "All right, I do nothing"
endif
echo "Have an nice day"
wait 10


I set protect test +s

On a CLI, no problem, correct execution in 1.3 or 3.1 and upper.

I add a project icon, set C:IconX as default tool
With 3.1 and upper, no problem, the script acts like a charm as under CLI
but with 1.3, the script ends on the ask line...
Is a there a way to workaround this
Thanks in advance.

[malko]

I think you will benefit from the adding of a line in your script, like this :

.key dummy/k
echo "Hello world"
ask "continue ?"
if WARN
echo "you are OK to continue"
else
echo "All right, I do nothing"
endif
echo "Have an nice day"
wait 10

[Thomas Richter]

Originally Posted by Gilloo

Is a there a way to workaround this
Thanks in advance.

Yes. Use kickstart 2.0 or better. This cannot possibly work under 1.3. The problem is due to a design issue of the BCPL shell and the dos Execute() function.


Problem is that for ask to work, it needs an input stream to read data from. Problem is that the only way how to start a shell (and that is the method IconX uses) is the Execute() function call. You can surely provide an input stream to Execute. However, if you do, the shell started by Execute() will continue reading from this input stream as soon as the command string has been operated on. Simply put, if IconX would provide an input stream, it would start a new shell and would continue waiting for command input after the script has been worked through.


Under 2.0, the shell, shell startup and dos.library were completey reworked, and the System() function call allows running a shell that returns if the command stream is exhausted, even if an input stream is present.


PS: Note that dos/Execute() has (almost nothing) to do with the Execute command. The latter does something very different (and, in particular, does not start a shell, just redirects its input).

[AMIGASYSTEM]

Hi Thomas Richter, for OS 1.3 is there also Xicon, start the Shell but seems not to work with that script ?

http://aminet.net/package/util/batch/Xicon

[Thomas Richter]

...and there is CLICon, which offers even more options, but again, see above. The trouble is not "how you do it". It is really a limitation of a shell. As soon as the 1.3 shell receives a standard input, and its command stream runs dry, it will continue pulling commands from CIS and hence will turn into an interactive shell. Actually, the "only" thing endcli does is to remove this standard input, and thus terminate the shell.

[malko]

And there is also just plain 1.3.3 Workbench (fresh install, air, sun - no OGM, no add-ons ) which works nicely with this script if you add a simple line in the beginning

[AMIGASYSTEM]

I had suspected that there was a missing option in Tooltypes.

[malko]

^ why do you think there was a missing option in ToolType ?
Because I used the same icon (thus ToolTypes) for the original and the modified version. Only the position of the windows is different.

[TCD]

Originally Posted by malko

^ why do you think there was a missing option in ToolType ?
Because I used the same icon (thus ToolTypes) for the original and the modified version. Only the position of the windows is different.

Because obviously it can't be as easy as adding one line to the script

[malko]

Originally Posted by TCD

Because obviously it can't be as easy as adding one line to the script

Sometimes it is

Originally Posted by Thomas Richter

[...] Under 2.0, the shell, shell startup and dos.library were completey reworked, and the System() function call allows running a shell that returns if the command stream is exhausted, even if an input stream is present. [...]

Was the 2.0 Shell really completely reworked ?
In the big lines I understood that it was "simply" the 1.3 NEWCON: that was integrated in the usual CON: (not to have like as with 1.3 CON: & NEWCON: ).

[AMIGASYSTEM]

Originally Posted by malko

^ why do you think there was a missing option in ToolType ?

I had used an icon created new with no commands in the tooltypes

[TCD]

Originally Posted by malko

Sometimes it is

I know Good luck!

[thomas]

Originally Posted by malko

Sometimes it is
In the big lines I understood that it was "simply" the 1.3 NEWCON: that was integrated in the usual CON:

CON/NEWCON is only the window handler. It has nothing to do with CLI/Shell.

It's rather l:shell-seg which was reworked/integrated into Kickstart.

[Gilloo]

Originally Posted by malko

I think you will benefit from the adding of a line in your script, like this :

.key dummy/k
echo "Hello world"
ask "continue ?"
if WARN
echo "you are OK to continue"
else
echo "All right, I do nothing"
endif
echo "Have an nice day"
wait 10

@malko Great !
with 34.20 the .key seems to be mandatory to make the script work correctly with IconX

Many thanks for your help.

[malko]

Originally Posted by thomas

CON/NEWCON is only the window handler. It has nothing to do with CLI/Shell.
It's rather l:shell-seg which was reworked/integrated into Kickstart.

Thanks for the precision.

Originally Posted by Gilloo

@malko Great !
with 34.20 the .key seems to be mandatory to make the script work correctly with IconX
Many thanks for your help.

You are welcome.

[Gilloo]

@malko
A small question that has nothing to do with the subject "IconX, Ask and WB1.3"
How you have captured the WinUAE output and transform it in a simple .gif ?
I thought we could only release it in .avi

[malko]

It's a two steps process :

1. Capture using GifCam
2. Clean/optimise/speed with Gimp (it could be done with GifCam but I am used to Gimp, so...).

Then upload where you want. I use 'imgbb' (free, convenient, fast & support animated gif (as well no auto-delete)).