Advanced Properties - Evaluation version 9 (048)

[Methuselah]

Hello guys - it's been about two years - I was still on version 7 at the work I just resigned from. Wow, things have changed in V9 - excellent stuff !!

Started automation at a new client today.
Got stuck trying to get rid of a troublesome error message.
Appears to be a system message - text is Unable to write to c:\Autrix.ini - access issue under WinXP pro - users don't have rights.

Anyway, I've done this before, so quickly knock up a little macro to kill the message. I set it to run on Window_Open under Advanced properties.

Here's the problems :-

1. The checkbox properties of "Visible windows only" and "Allow scheduler service" are either never saved, or they are reset next time I go look at the properties.

2. If the message is present when the properties are updated, it is removed as expected. If the macro is simply "run" when the message is present, all is okay.
What is not working is if the message is issued at other times.
I suspect the WINDOW_OPEN event is never being recognised - and the macro is not being run.


Is this now standard behaviour in version 8/9 ?
Text does say if window title "present", not "on open" ?

Anyone else spotted similar funnies ?


(I will get the sys admin to add rights on the workstations - but MSched V9 eval didn't cut it - I'll try a V7 trial tomorrow to check if it still works on that release - or is system/setup related )

Robin.
Jhb, South Africa

[pgriffin]

Allow me to ask the obvious question. When you set the advanced settings, you are pressing the OK button to dismiss the Properties dialog?

Otherwise, I can't imagine why the properties would not be saving. After saving changes, take a look at the date/time stamp of Macros.dat to see if it is being updated.

[Methuselah]

. . . obvious question . . . pressing OK

Yeah, things go like that sometimes. Especially after really wanting to have the settings saved. I even went so far as to bounce MSched in case it had gotten itself in a knot. I'll check if there's another way to dismiss the dialog. (Like a Cancel / Okay switch ).

Can I ask the reverse then as well, please . . . does this work for you guys not on an evaluation version of release 9 ?

I'll also have a look at Macros.dat properties.
Certainly other settings are being remembered, so that may answer the questions about it being a display reset on dialog presentation.

[pgriffin]

I have run eval version 9 as well as currently running full msched pro version of v9 and haven't had this problem in either version.

[Methuselah]

Solved - Well, kinda.

After install, using Admin userid, the program lives under Program Files.
The user-level userid does not have update rights to this folder.
They can, however, create, so it's LOOKS okay until you want to change something.
Skunkworks, you had it spot on - macros.dat access.

It's not something easy to spot - tried creating the macros under Admin and copying it to the user folder and subdir as well. Again user has no update access, but is allowed to create a copy (!!!) under the main Msched folder.

So: I guess giving all users update access to macros.dat is imperative.

[Marcus Tettmar]

Not sure what you are talking about here as Macro Scheduler will create a data folder under the user's My Documents folder if run under a limited user account. You should see macros.dat in your My Documents\Macro Scheduler folder.

If not, could be due to having previously had a beta version running, when there were some differences/bugs. If that is the case I would strongly recommend a complete uninstall and then reinstall. Install under Admin and then run under a limited user account and you will then see all the macros and data files in My Documents\Macro Scheduler folder.

[Methuselah]

'Ello

Will remove and re-install.
Gonna buy the real version anyway, so will do that first.

l8r
Robin.

[Marcus Tettmar]

Regarding the "Only When Visible" and "Allow Scheduler Service to Run this Macro" check boxes we have identified a bug in both cases that will prevent the change being saved. We are fixing this in build 050.