How to remove macro from the All Macros listing

Me_again · Post by **Me_again** » Wed Mar 18, 2009 10:12 pm

Sorry for a really basic question but I'm permanently confused about how macroscheduler stores and lists macros. How do I remove macros from the "All Macros" listing, without deleting them? I don't see any option to do that. (I have 9.1 if this has changed recently.)

jpuziano · Post by **jpuziano** » Wed Mar 18, 2009 10:40 pm

Hi Me_again,

Can you tell us why do you want to remove the macro from "All Macros"?

You could assign it to a Group... but then it would be listed both in that Group and when you clicked on "All Macros" so perhaps you don't want to do that.

And you don't seem to want to delete it... however it has to show up somewhere... or how would you access it from the MS main window?

I am curious both in what you're after and the answer/s you'll get as I have an enhancement request somewhat related to this:

[Open] Ability to Sort Groups and change back to 'No Group'

Take care

Me_again · Post by **Me_again** » Wed Mar 18, 2009 11:05 pm

To stick with the short and mostly non whining version, I somehow ended up with a lot of old .scp's listed in the All Macros group. It would help if I could see in which directories the listed macros are actually stored, but I haven't figured out how to do that, and opening in the advanced editor and using Save As doesn't default to the original directory either. I was smart enough to test "Delete" and determine that it really deletes the file itself rather than just removing it from the listing.

Bob Hansen · Post by **Bob Hansen** » Wed Mar 18, 2009 11:40 pm

I know that I have a number of files in a Group or the Common folder that do not show up in the listing, and that's the way I want it. There are some scripts that I do not want visible, but may want in the future. So I keep them there, and then when needed I just do an import.

I haven't checked this out, but to remove from the listing now, try this:

1. Copy the scripts you don't want listed to another temp folder.

2. Now delete the scripts from the Groups/Folders using normal Macro Scheduler menu commands.

3. When listings look correct, then move the scripts from the temp folder into the folders where you want to store them.

4. When all are moved, you could delete the temp folder.

5. The scripts should now be in the correct folders but not visible until you import them.

jpuziano · Post by **jpuziano** » Wed Mar 18, 2009 11:41 pm

Hi Me_again,

The following post talks about removing a macro from a particular group while not actually deleting the .scp file:

Remove from group: http://www.mjtnet.com/usergroup/viewtopic.php?p=23219

If you're trying to find out what groups those .scp files used to belong to... I think that info might be stored in your groups.dat and macros.dat files.

Some info in this post may help: http://www.mjtnet.com/usergroup/viewtopic.php?t=3324

Take care...

Me_again · Post by **Me_again** » Thu Mar 19, 2009 12:06 am

jp: Thanks for the links, Edit, Remove From Group, will do what I want

Bob: If I knew which folders they came from I probably wouldn't be in this mess

jpuziano · Post by **jpuziano** » Thu Mar 19, 2009 1:05 am

Hi Me_again,

There's another option if you still want to find out which groups that certain macros used to belong to.

Macro.Dat reader
http://www.mjtnet.com/usergroup/viewtopic.php?t=2891

If you still have the old macro.dat file kicking around... why not run that script and see what you can see. Note that the script points to where your working macro.dat file will be... but if you have an old copy of your macro.dat file saved somewhere else, you might change the script to point to it instead.

If the macro name is found then it can show you what group was associated.

I'm not sure if JRL has a newer version of this script, but it still works and helped me out a time or two... thanks again JRL.

Take care

Me_again · Post by **Me_again** » Thu Mar 19, 2009 1:59 am

It's not the groups that are my problem, it's the (multiple) locations where the files are actually stored. If "Save As" in the editor defaulted to the same folder as the file being edited I wouldn't get into as much trouble. If importing a macro to a group (from some other folder) just maintained a link to the original and didn't create a second copy then I wouldn't get into as much trouble. Mea culpa