Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wisp
« on: June 03, 2017, 04:46:23 AM »

It'd be a fair bit of work uncoupling AT_* VIEW from the other AT_* (which must run synchronously), for what I perceive to be very little gain. With the introduction of README long ago, AT_* VIEW  is effectively deprecated.
Posted by: AL|EN
« on: May 31, 2017, 02:30:52 PM »

Maybe it's better idea to have AT_* ~VIEW something~ to not wait for external process to exit? The "--skip-at-view" might be still need to stop opening webpages/redme every time when mod/component will be reinstalled.
Posted by: Wisp
« on: May 31, 2017, 02:20:19 PM »

--skip-at-view, --no-exit-pause. If it does not widely make mod installations crash and burn (like disabling inferior processes would), I can add options for other things, as well.
Posted by: AL|EN
« on: May 31, 2017, 01:53:29 PM »

First thing which comes to my mind (there might be others) is AT_INTERACTIVE_EXIT ~VIEW ModName/readme.txt~ - it will block further installation until somebody will close Notepad/Editor. Please get rid of it to make sure that 'not optimal coding'  ;)  can't mess with installation process. I'm also questioning weidu ability to run external process but that's other story.