Please Delete - issue resolved

Dman · Post by **Dman** » Tue Apr 07, 2009 2:57 am

Please Delete

Post by **Marcus Tettmar** » Tue Apr 07, 2009 4:08 pm

This is REALLY unhelpful. The whole point of forums for me is that when an issue is resolved people can see what the issue was and what the resolution is. People may have similar issues and may be searching for a solution and the forum post may help them. Deleting issues that are resolved does not help anyone.

klcmay · Post by **klcmay** » Tue Apr 07, 2009 5:16 pm

Couldn't agree more!

In fact you helped me out with an issue many months ago... it was so long ago that I had forgotten what the solution was and still having the thread available was most helpful in refreshing my memory!

Dman · Post by **Dman** » Wed Apr 08, 2009 1:01 am

mtettmar wrote:This is REALLY unhelpful. The whole point of forums for me is that when an issue is resolved people can see what the issue was and what the resolution is. People may have similar issues and may be searching for a solution and the forum post may help them. Deleting issues that are resolved does not help anyone.

This was a post about a problem with mousemoves not working, but the root cause was an upgrade from Macro Sched 10 to 11, hardcoded path to the old Macro Sched directory that a corporate environments roaming profile kept creating & overwriting directories even when removed.

I understand the importance of sharing knowledge, so much so that I maintain a KB where I work, however this was isolated with a root cause not relating to Macro Scheduler, hence why I removed it. The only feedback is that if the directory didnt change from "Macro Scheduler" to "Macro Scheduler 11" in the upgrade, the include paths in my macro wouldn't have been incorrect.. but I'm sure there is a good reason for that change, and it was a roaming profile that kept the issue going.

Bob Hansen · Post by **Bob Hansen** » Wed Apr 08, 2009 3:30 am

Thanks for that info Dman.

Your comments provide a lot of clues that people can use if they have a similar problem. The different directory is not related at all to Roaming Profiles, but it raises an awareness to all others doing an upgrade.

It also suggests using variable paths vs. hard coded paths.

And Roaming Profile effects on any application is another topic that you have raised.

Lots of good stuff.

Dman · Post by **Dman** » Wed Apr 08, 2009 4:22 am

The issue was that the romaing profile kept putting the "Macro Scheduler" directory back even after I deleted it meaning I couldn't effectively diagnose it was pointing to the old directory in all of my macros.

I would whack up a case study of it but the post was looooong. Depends how many people want the full story.

Bob - varaible paths?

Bob Hansen · Post by **Bob Hansen** » Wed Apr 08, 2009 5:39 pm

Bob - varaible paths?

(You misquoted me, gave me a spelling error).

Variable paths, like these:
Built in with Macro Scheduler
%Win_Dir%
%Script_Dir%
%Desktop_Dir%
%Temp_Dir%
%Sys_Dir%

Samples of some others from the Environment
GetEnvVar>HomePath,vHomePath
GetEnvVar>UserProfile,vUserProfile

Please Delete - issue resolved

Please Delete - issue resolved

Seconded!