Brando569 Posted June 14, 2005 Posted June 14, 2005 the menu options fly by too fast is there any way to slow them down? i tried using sleep but instead of displaying whats happening it says "executing sleep"
Wraith Posted June 14, 2005 Posted June 14, 2005 Add a display="..." to the sleep with the display of the previous tag.I don't see why people would want to pause execution.....
Brando569 Posted June 15, 2005 Author Posted June 15, 2005 (edited) Add a display="..." to the sleep with the display of the previous tag.I don't see why people would want to pause execution.....<{POST_SNAPBACK}>so we can see what its actually doing editi just re read that, do you mean add display="..." to <execute> <program>sleep</program> </execute> ? Edited June 15, 2005 by Brando569
Nanaki Posted June 15, 2005 Posted June 15, 2005 Yup, something like this:<execute display="zzzzzzzzzzzz..."><program>sleep</program><arguments>2000</arguments></execute>
Brando569 Posted June 22, 2005 Author Posted June 22, 2005 thanks but that will add "executing zzzzz...." i want sleep to be silent and have it display the things it has done before excuting sleep, if that makes any sense
Nanaki Posted June 23, 2005 Posted June 23, 2005 Not possible atm. The workaround would be to take a seperate batch and put the installer and the sleep in there. :/
Wraith Posted June 23, 2005 Posted June 23, 2005 It's not possible in the way that you want it, nor will it be possible at all.XPlode clears the display before going to another plugin, and it's my view that people will want things to run as fast as is possible, not stopping to show some information that in all seriousness, is irrelevant.You're the only person that seems to want it to pause, if I get a LOT more requests I'll consider it, but at this stage, not going to happen.
Maelstorm Posted July 4, 2005 Posted July 4, 2005 If I may interject something here...I would suggest that you use the /log command line option if you want to see what it's doing.xplode.exe /log:"%SYSTEMROOT%\XPlode.log"That would be the way that I would do it. With the log file, you can then study it for as long as you want to, and if any errors happen, they will also be in the log file. (Along with commands executed, status messages, etc...)
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now