Jump to content
Macro Express Forums

floyd

Members
  • Posts

    292
  • Joined

  • Last visited

Posts posted by floyd

  1. Frankly, in my opinion and based on my understanding, a command like "Wait for text playback" which doesn't appear to have any function outside of the Text Type command shouldn't even exist outside that command.

    It is probably like this for backwards compatibility. Over the years, Macro Express has morphed from a handful of commands to what we have now. In each new major release, the underlying file and command structure (the MEX file) has changed dramatically. But converting has always been easy because they attempt not to break anything by deprecating old commands. They may also feel that it is a command that users are used to having and did not want to rock the boat.

     

    Having a Wait for Text Playback checkbox in the Text Type command is a nice idea and you should suggest it if not having done so.

  2. It makes no sense to Wait for Text to Playback for a single key Alt+F4. The command was designed for situations where the Text Type command could overflow the keyboard buffer. MX Pro, like its predecessors, can push characters into the keyboard buffer faster than the targeted program can extract them. So in order to Text Type long paragraphs into a Word document use Wait for Text to Playback between paragraphs, but don't use it for things like Alt+F4.

  3. Can you do a more typical folder move, like my example?

    The key to moving a folder to a non-existing target (a folder that does not yet exist) is to leave off the trailing backslash in the Destination Path/Name field. The trailing backslash in the File(s) Path/Name field doesn't matter, at least not in this case. So your example would work if written like this:

    <MOVE FILE/FILES Source="C:\\temp\\Subfolder1\\" Dest="C:\\NewDestination" Progress="FALSE" Recurse="FALSE"/>

    If you leave the trailing backslash in the Destination Path/Name field then the files will be moved to the target destination, but the source folder itself will remain.

  4. So ... mouse click problem not in MX 3 but in MX Pro? Is that what you are saying? We have come full circle, I think.

     

    ===============================================================================
    Macro Express Pro v 4.0.1.1
    ===============================================================================
    54. Fixed a bug where swapped mouse buttons didn't work correctly.

    Let's assume for the moment that the above fix in 4.0.1.1 does indeed address the problem you had, and are having. I am not sure ISS means they fixed a conversion problem or they fixed an internal MX Pro problem. If it is a conversion problem, and you converted you MX3 macros prior to the above release, then maybe converting them again will resolve the issue.

     

    If it not a conversion problem,and you are convinced that the mouse buttons are switched, then try the direct editor. Use its features to swap the click commands: <MOUSE RIGHT CLICK/> and <MOUSE LEFT CLICK/>.

  5. It is easy to unintentionally thread-jack posts especially in a programming forum. So okay ... stop it. Thank you.

     

    To answer the topic title, yes, Wait for Text Playback is very reliable. Although I do not have any direct knowledge of its implementation, I assume the intention is to simply halt the macro until the keyboard buffer returns NULL or is empty. Never had a problem with it. Ever.

     

    To the other, er, speculative comments. You are overrunning the keyboard buffer. Macro Express can feed the keyboard buffer a gazillion times faster than the application you are typing to can extract the characters. So use Wait for Text Playback after sending a handful of data to the buffer OR use the Keystroke Speed command which sets a delay between each character fed into the buffer OR use both commands.

  6. This must be a common requirement for FF users, so I'm wondering if anyone has some finished macro(s) they might share please, so that I don't set about re-inventing the wheel?

    I strongly suspect that if this were easily doable, ISS would have done it by now given the hundreds of requests for it. I know that is not an answer, but it is a warning that you could spend a lot of time on it.

     

    On the other hand, it is perfectly doable using IE.

  7. Well, this is exciting. I didn't know that I was going to stir up so much reaction.
    Thanks. We try to keep the excitement level, you know, up there. Truly, we do.

     

    Anyway, my goal was to resize the window so that it occupied the whole screen except for the screen area occupied by the taskbar. Now if the taskbar happens to be hidden via autohide, then the window would occupy the whole screen. But this would be accomplished by resizing the window not just maximizing it.
    I see. So maximizing without, er, maximizing. Got it. Seems that we need to find a way to determine desktop client height and width rather than just desktop height and width.
  8. FLOOOOOOOOOOOOYD! "Good morning, Worm your honor!" I haven't heard from you in a coon's age. How ya been? You ever noticed how people don't like answering your questions? :) "Call the schoolmaster!" I actually watched the movie two nights ago, sorry.

    It's good to be back. I see things have changed er, very little. Was feeling Comfortably Numb for a while and then I went on the Run and ended up on the Dark Side of the Moon .. were I was Wish[ing] You Were Here. ;)

     

    Always good stuff Cory. Thanks. And thanks for filling the void! I guaranteee it is appreciated by all!

     

    Well I've been playing with Macro Express Pro for a while now and I find it to be a tremendous tool. This, despite some obvious and inconvenient bugs. I have faith that ISS will do their usual good job of making things better. They've never failed me yet in all these years.

     

    And my oh my ... but that External Script command just, well, it just brings a tear to my eye.

     

    But okay ... I don't want to thread-jack this fella's post.

     

    ---------

     

    Well your solution seems plausible except that it would create an unwanted "flash" and it would only work if the "Keep the taskbar on top of other windows" box was checked (Taskbar Properties dialog).

  9. The binary value in HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\StuckRects2 is only updated when you log off and back on to Windows. If the user has changed the Auto Hide taskbar setting StuckRects2 will not reflect the AutoHide status.

    Kevin is absolutely correct, which is why I could not recommend the solution. So let me repeat my question so we can help find the correct solution:

     

    Is the goal then to maximize a window as if the taskbar was showing whether or not it is?

  10. Does anyone have a way to detect whether or not the windows taskbar is currently displayed or hidden (via autohide)? I have a macro that resizes and repositions the current window so that it maximizes the window but doesn't cover the taskbar. It detects what side (left, right, top or bottom) the taskbar is on and how much the of the taskbar is exposed. The only time it doesn't work is when the taskbar autohides. I haven't been able to detect whether or not if the taskbar is hidden or not.

    Is the goal then to maximize a window as if the taskbar was showing whether or not it is?

  11. I started out by explaining that AFTER running any macro, there's a `dead' period during which no other macro will run. Yet all the responses are based on the idea that the first macro is in fact still running, which amounts to a different problem description. So I ask again that we leave it there. But I'm very grateful for the responses.

     

    Let me get this straight ...

    1. You ask for help
    2. State what the symptoms are
    3. Refuse to answer any questions that might help us help you
    4. Accuse those willing to help of changing your problem's description
    5. Then write that you are "grateful"?

    What a crock. <EDITED>

  12. I attached two 24x24 icons one with 256 and one with 18.6 M Colours. If you try out the two icons, you´ll see what i mean.

    They seem to be working for me. Attached is a picture of what I'm seeing.

     

    By the way. If i change the appearance of an used icon, i have to restart MEX in order to see the changes, right?

    I'm not sure, but I would think not because the icons are not embedded anywhere.

    post-3-1197992897_thumb.jpg

  13. Double click... does not. It will not even click on the control. Sorry if this has been previously covered. Ideas? I have tried using different mouse speeds, etc.

    Not sure what is happening. I set up a test with the calculator and got the same results as you.

     

    I'll create a bug report and send it to Insight. In the mean time, two single-clicks in a row can be used as a work-around.

×
×
  • Create New...