Dialogs failing in version 033

Technical support and scripting issues

Moderators: Dorian (MJT support), JRL

Post Reply
Guest

Dialogs failing in version 033

Post by Guest » Fri Apr 25, 2003 10:48 pm

I have just installed version 033 and found that my Dialogs no longer work. The object names no longer are picked up. This was working OK in version 032. Data is entered into the Edit box and selections made from the Combo boxes.
====================
The major part of the Dialog portion of the script is the following:

Label>Proceed
Let>DefaultAction=Log Off
Let>WindowsExit.Action=%DefaultAction%
Let>DefaultReason=Normal-end of work
Let>WindowsExit.Reason=%DefaultAction%
Let>DefaultOther=

Dialog>WindowsExit
Caption=Shut Down Windows
Top=144
Width=315
Left=312
Height=230
Label=What do you want the computer to do?,56,16
Label=%ComboHelp%,34,72
Label=Reason:,21,112
Label=Enter Other Reason / optional Note,125,112
Button=OK,28,160,75,25,1
Button=Cancel,120,160,75,25,2
Button=Help,212,160,75,25,3
ComboBox=Action,82,40,145,%DefaultAction%%CRLF%Re Boot%CRLF%Shut Down
ComboBox=Reason,8,128,121,%DefaultReason%%CRLF%Low Resources%CRLF%Problem noted here:%CRLF%Required by System%CRLF%Software Change%CRLF%System is hung%CRLF%Testing%CRLF%See Other Reason:
Edit=Other,136,128,164,%DefaultOther%
EndDialog>WindowsExit

//Prompt User to select method of Shutdown
Label>ShowWindow
Show>WindowsExit,Button
===========================
It looks like the processing sequence may have changed because in version 032 I see BUTTON=1 happens before WINDOWS.EXIT.OTHER is calculated. In version 033 I see all these WINDOSW.EXIT.MSxxx items calculated before the BUTTON=1 happens. Note everything above DOW=Friday (reference to version 032 is the data that was typed into the Edit box).

Here is part of a snapshot of the watchlist in version in version 032
WINDOWS.EXIT.OTHER=version 032
BUTTON=1
DOW=Friday
This is a snapshot of the same script watchlist run in version 033
BUTTON=1
WINDOWS.EXIT.OTHER=
WINDOWS.EXIT.MSBUTTON6=Help
WINDOWS.EXIT.MSBUTTON5=Cancel
WINDOWS.EXIT.MSBUTTON4=OK
WINDOWS.EXIT.MSLABEL3=Enter Other Reason / optional Note
WINDOWS.EXIT.MSLABEL2=Reason:
WINDOWS.EXIT.MSLABEL1=Log Off allows Log on as a new user.%CRLF%Shut Down turns off power.%CRLF%Re Boot restarts computer
WINDOWS.EXIT.MSLABEL0=What do you want the computer to do?
DOW=Friday
=============================
I have conditional programming based on WINDOWS.EXIT.OTHER which no longer works. In 032 I get back the value entered into the Edit box. In 033 the value entered into the Edit box is lost.

User avatar
Bob Hansen
Automation Wizard
Posts: 2475
Joined: Tue Sep 24, 2002 3:47 am
Location: Salem, New Hampshire, US
Contact:

Post by Bob Hansen » Fri Apr 25, 2003 10:51 pm

Note that the previous message re Dialog errors in version 033 was entered by me. I did not notice that I was not logged in.
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!

User avatar
support
Automation Wizard
Posts: 1450
Joined: Sat Oct 19, 2002 4:38 pm
Location: London
Contact:

Post by support » Sat Apr 26, 2003 1:09 am

Hi,

This has been fixed in build 034.
MJT Net Support
[email protected]

User avatar
Bob Hansen
Automation Wizard
Posts: 2475
Joined: Tue Sep 24, 2002 3:47 am
Location: Salem, New Hampshire, US
Contact:

Post by Bob Hansen » Sat Apr 26, 2003 1:38 am

Using 7.2.034 with Win98ME.

That was fast work, and well done!. Dialog problem has gone away. Thanks again. :D

But....when I ran a script calling a Dialog to Logoff, the Macro Scheduler Control Panel stayed on the desktop. I ran the script from the MS Control Panel, highlighted the script, and clicked on the Run icon. Dialog came up, Logoff was processed, all of desktop cleared except the MS Control Panel. When the Login window appeared it was on top of the still visible MS Control Panel. This is a repeatable problem, happens every time.
Hope this was helpful..................good luck,
Bob
A humble man and PROUD of it!

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts