Sign in to follow this  
Followers 0
Brando569

slowing stuff down

8 posts in this topic

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"

0

Share this post


Link to post
Share on other sites

Add a display="..." to the sleep with the display of the previous tag.

I don't see why people would want to pause execution.....

0

Share this post


Link to post
Share on other sites
Add a display="..." to the sleep with the display of the previous tag.

I don't see why people would want to pause execution.....

so we can see what its actually doing :)

edit

i just re read that, do you mean add display="..." to

<execute>

<program>sleep</program>

</execute> ?

Edited by Brando569
0

Share this post


Link to post
Share on other sites

Yup, something like this:

<execute display="zzzzzzzzzzzz...">
<program>sleep</program>
<arguments>2000</arguments>
</execute>

0

Share this post


Link to post
Share on other sites

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

0

Share this post


Link to post
Share on other sites

Not possible atm. The workaround would be to take a seperate batch and put the installer and the sleep in there. :/

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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...)

0

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.