http://bugzilla.wpkg.org/show_bug.cgi?id=155
Jason Oster <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Jason Oster <[email protected]> 2009-04-20 16:23:57 --- Maybe an additional XML attribute along side cmd attributes could help? flush="false" or similar? <install cmd='%COMSPEC% /c start "AutoIt3" "%PROGRAMFILES%\AutoIt3\AutoIt3.exe" "%PROGRAMFILES%\AutoIt3\redemption.au3" flush="false"' /> This would run the command like it did before r50, by skipping over the flush code. Alternatively, make the flush opt-in by adding flush="true" to commands which need it. I like the idea of keeping the flush available, because it sounds useful. (For debugging, and also for executing commands like extracting a large amount of files with the 7-zip command line app.) I've had to execute 7z.exe with "%COMSPEC% /c start" to get around the bug that the flush was designed to solve. Only downside to handling this with an attribute (that I can think of at the moment) is that it would be impossible to do both (flush + fork) in a single command. But this case might be exceedingly rare. What do you think? -- Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. ------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list [email protected] http://lists.wpkg.org/mailman/listinfo/wpkg-users
