In v6.0.0.3 it is possible to completely hide the progress screen through the variable %ShowActionProgressDlg%. (Can be toggled on/off between the screens.) I am a somewhat disappointed with the selected solution.
On 01-12-2002 Mark wrote: "From a design perspective we chose to show the Progress Screen to provide a seamless installation to the end user. This way there is always a "Screen" in the background, if we removed the Progress Screen, all the end user would see is a floating Message Box." This is correct if the Dialog action is performed. When running other actions, nothing is displayed at all; not even the hourglass cursor is displayed (seems to be bundled to the progress screen, not the perform action event). Think of actions running for two minutes! Still I want the possibility to toggle between a text/progress bar screen, or eventually a message box (editable) not requiring any user interaction (NOT the Windows API Message Box).
I think Lorne had the best suggestion (11-27-2001): "Actually, there is a workaround that you can use to do something pretty darn close to what you asked...but it involves a bit of work. The message IDs in the english.lng file are actually handled internally as variables...so, you can change the messages at run time by assigning different values to the IDs."
Previously I had a flickering screen with constantly changing the text (MSG_PROG_PARSE_STRING / MSG_PROG_CHANGE_FILE_ATTRIB) in a While-loop. By changing these variables to the same value, the screen at least had a steady appearance.
I know other designers have asked for the possibility to hide the screen. I should like to learn about how they implement this feature.
On 01-12-2002 Mark wrote: "From a design perspective we chose to show the Progress Screen to provide a seamless installation to the end user. This way there is always a "Screen" in the background, if we removed the Progress Screen, all the end user would see is a floating Message Box." This is correct if the Dialog action is performed. When running other actions, nothing is displayed at all; not even the hourglass cursor is displayed (seems to be bundled to the progress screen, not the perform action event). Think of actions running for two minutes! Still I want the possibility to toggle between a text/progress bar screen, or eventually a message box (editable) not requiring any user interaction (NOT the Windows API Message Box).
I think Lorne had the best suggestion (11-27-2001): "Actually, there is a workaround that you can use to do something pretty darn close to what you asked...but it involves a bit of work. The message IDs in the english.lng file are actually handled internally as variables...so, you can change the messages at run time by assigning different values to the IDs."
Previously I had a flickering screen with constantly changing the text (MSG_PROG_PARSE_STRING / MSG_PROG_CHANGE_FILE_ATTRIB) in a While-loop. By changing these variables to the same value, the screen at least had a steady appearance.
I know other designers have asked for the possibility to hide the screen. I should like to learn about how they implement this feature.
Comment