@LiveForIt
Thanks for your help
Quote:
does your mount list look like this?
yes
Quote:
Mount KCON: from DEVS:KingCON-mountlist
Mount KRAW: from DEVS:KingCON-mountlist
do not dismount CON or RAW, just keep it as it is.
make a copy of sys;system/shell
rename the copy to "kingcon_shell"
check the icon tooltype
Change this line:
WINDOW=CON:50/50/600/350/AmigaShell/CLOSE
to:
WINDOW=KCON:50/50/600/350/Kingcon/CLOSE
save "kingcon_shell" icon settings.
This was approximately how i was using KCON and CON side by side before i tried switching them altogether/
I may revert to it? What i was after was having the best ability to detect problems with KCON that i wouldn't have with CON.
My problem is that the output windows are generated by 2 integrated apps
the loader for Gui4Cli & Gui4Cli itself. I wondered if there was interference with KCON that i did not have with CON.
Switching radically between them at satartup looked like the best method, as i wanted to use the same console type, whatever way i launched gui (the loader), gui4cli or a gui4cli script (eg from the Workbench execute menu (***) , the local menu, cli, workbench)
In the first program (gui.c) i have for example the 2 first lines below, in Gui4Cli the last lin, plus writing commands making use of this spec (or other provided by command line eg KCON: or tooltype.
It was using the last possibility that i started having problems
strcpy (output, "con:0/12/400/80/Gui4Cli/auto/close/wait");
Write (Output(), "WB2.04+ Only!", 13);
strcpy (Defconsolespec, "con:300/20/450/80/Gui4Cli Output/CLOSE/AUTO/WAIT");
(***) I had to add a Newshell command in the user-startup to make the workbench execute menu produce KCON output
It now looks like
requestchoice >ENV:rcnum "CON: or KCON:"choose CON|KCON
IF $rcnum EQ "0" VAL
Assign CON: DISMOUNT
Assign RAW: DISMOUNT
Mount CON: from DEVS:KingCON-mountlist
Mount RAW: from DEVS:KingCON-mountlist
Newshell
ENDIF