#144923 - 2005-08-09 10:17 PM
Re: Break On should be the deafult
|
NTDOC
Administrator
   
Registered: 2000-07-28
Posts: 11622
Loc: CA
|
Not implying you have poor coding skills. But I do notice that each time you post a suggestion you do approach it with a very strong passion that is not satisfied until the topic dies of age or you get your way. Were you a politician in another job? 
I guess I'll fall back to previous answers then. Change it anyway you want, I can code around it.
|
Top
|
|
|
|
#144928 - 2005-08-10 09:17 AM
Re: Break On should be the deafult
|
Richard H.
Administrator
   
Registered: 2000-01-24
Posts: 4946
Loc: Leatherhead, Surrey, UK
|
Quote:
sure, but I hate those stupid best practise comments on BREAK ON when it doesn't even work.
Well then get it fixed 
Changing the default action of every script that's out there to fix another problem is not the right way to go about it.
I can see no reason why the "BREAK" statement should not affect the kill settings of WKIX32. Ok, so if there is no console so you cannot install the SetConsoleCtrlHandler() to deal with control-C which is fair enough. However that is no reason that the "logoff when killed" action should not be affected by the BREAK statement.
You need to petition Ruud (again?) to get wkix32 fixed.
|
Top
|
|
|
|
#144938 - 2005-08-17 06:48 PM
Re: Break On should be the deafult
|
Bryce
KiX Supporter
   
Registered: 2000-02-29
Posts: 3167
Loc: Houston TX
|
Quote:
so, is it ruuds laziness if he can't make the "break off" default only during login? outside logon procession, it would default to "break on"
this is a good point... well not that Ruud is lazy!!!
Ruud added a macro @LOGONMODE that is true if the script is running as a logon process, could not the "break" be coded the same way?
this keeps the default "break off" for logon scripts, but gives the admin script a "break on" enviroment.
|
Top
|
|
|
|
Moderator: Lonkero, ShaneEP, Jochen, Radimus, Glenn Barnas, Allen, Ruud van Velsen, Mart
|
0 registered
and 418 anonymous users online.
|
|
|