Jump to content
Macro Express Forums

warrentheo

Members
  • Posts

    8
  • Joined

  • Last visited

Posts posted by warrentheo

  1. I'm not sure I'm the best person to answer this but how are you copying the filenames? Just selecting in Explorer won't work as far as I know. If you click the name, short delay, click again, (+ Shift+End in Opus), Ctrl+C that will copy the text name. Other 3rd party XP shells (eg ExplorerXP or Directory Opus) will copy the file name or complete filepath to the clipboard with a few (macro?) key presses. I don't know how many times I've used the full filepath utility in DO while making macros! I don't have Vista or W7.

     

    I have Win7x64, but have a copy of the XP Clipboard viewer, it shows full file name/path when I copy the file.  When I use that program to save the contents of the clipboard, then open them in notepad, it shows the same file name buried in the middle of the garbage and shell extensions stuff used by windows to know it is a file and not text.  I was just wondering if there was a way to get that same info to a variable in MXP?

  2. Hello, I am in the middle of writing a macro, that processes info found in the clipboard.  It works just fine when it finds simple text in the clipboard, but I also want it to work by parsing text files passed to it by copying their name in explorer or something similar.  I have the XP clipboard viewer, which says that the clipboard just contains a simple string with the location of the file copied (I realize that it is anything but simple text, and is just being displayed that way).  When my current macro hits this kind of info in the clipboard, it reads nothing at all, and the macro exits as it has no data to run from.

     

    What I am looking for is a way to extract the file name and location from the clipboard when it occurs.

     

    Your help is appreciated, and I thank you in advance :)

     

    EDIT: Haven't done much with them, but is this the sort of thing "Control" class variables are for?

     

     

     

    This is what I am using currently:

     

    <VARIABLE SET STRING Option="\x02" Destination="%T[1]%"/>

  3. No simple way to do it.

    .........................................

    As far as I know there is no place in the macro where you could save the macro information so that it would be accessible from the outside by accessing the MEX file. However you could Export > Output Macro Information and access stuff in the macro. EG I would write a macro that would Output Macro Information and export only the macro name and script. Then you could have a comment in the first time and create a macro to parse the output file. Or just use the macro name. The downside is that you would have to run this every time you create a new macro.

     

    I've done something similar to this to search for text across all macros. If you're interested I could make you a macro like I described for pretty cheap.

     

    Ah, that was probably what I was looking for, I will look into it.  Thank you very much, you help is appreciated  :lol:

  4. Information isn't stored inside macros..........

     

     

    If you have a macro that sets a variable with a specific value, then that value can be retrieved using one of the "Save Variable" commands in the source macro, and "Restore Variables" command in the calling macro.

     

    Other options include storing the information in a .txt file on your hard drive. Or an .ini file. Or using the Write to and Read from Registry commands.

     

    By the way: Thanks for stealing my icon ;) I've been looking for an excuse to change mine anyway.

     

    Lol, sorry :-P

     

     

    I was hoping for a quick and easy way to store this info with the macro it goes with, and read it from outside that macro without having to run every macro.  Will the Save/Restore Variable work if the original macro has never been run?

  5. Hello all, I am writing a new macro that will use information stored in each macro to generate a second file for launching that macro.  I have been trying to figure the best way for storing this info along with each macro.  The way that currently comes to mind is to put a specially formatted comment line at the top of the macro, and use my new macro to parse all macros in a given .mex for these comment lines.  Unfortunately, I am unable to find a way to parse all macros, or read them from another macro at all.

     

    I was hoping someone could point me in the correct direction, or possibly suggest a better way of storing this info (trying to avoid a third file that has to be edited manually).

  6. Small, but probably unhelpful update, the windows mouse drivers can't actually be used for those extra keys, most likely they are installing both a mouse driver for controlling the main 3 mouse buttons and wheel, then install a keyboard driver for the rest of the buttons.  This means that it counts as a second keyboard most likely, and if you knew how to read it you could program it, but this would require being able to hack driver code and such, beyond most mex programmers I think... Sorry.

  7. I to am using Windows Speech Recognition, and find it to work very well (Win7 x64). There is a Windows Speech Recognition Macros add-on put out by Microsoft, but it is very clumsy, and barely functional. It stores the macros as individual XML files in your Documents folder, and is edited as XML as well (no editor, and only the most basic creation wizards).

     

    I looked this up, but there have not been that many people asking about this, this is the only Link I have found on it.  :o

     

     

    However, I think it would be quite simple to create a macro that would read every macro and see if it sees a special comment line for a spoken activation string, then generate the XML activation files with a simple template.

     

     

    This would work, and be fairly easy to write, but would have a few downsides

     

    1.  You would need to install WSRMacros just to get it to work, (Small price, the file is free from Microsoft, but annoying) and,

     

    2.  You would need to re-run the activation registration program each time you updated a macro to save the changes (also annoying, and with a lot of macros, potentially very time consuming)

     

    I am wondering if there is a simpler activation method for MX than this, any help in the right direction would be appreciated :)

     

    Also, there should be a command line for speaking text out loud in windows, but I am having difficulty finding it (basically trying to integrate the speak it macro program into this one, but without an exe file required)

×
×
  • Create New...