terrypin Posted August 24, 2015 Report Share Posted August 24, 2015 This is best explained with an illustration: I haven't confidently pinned down the cause, and I cannot reproduce at will. I only realise it's happened when my macro fails (because it expects a maximised window) and on investigation I see the state shown. But I'm posting here as I'm fairly sure it has only arisen while writing macros for IrfanView which include Window Maximize: <Current Window> Anyone seen similar please? Assuming it is down to MX, easiest work-around suggestions? --Terry, East Grinstead, UK Quote Link to comment Share on other sites More sharing options...
acantor Posted August 24, 2015 Report Share Posted August 24, 2015 I occasionally notice windows that are unusually sized, just like the one you show. I wonder whether we are both seeing an unintended side effect of MEP's Maximize Window command. Try substituting: Text Type (Simulate Keystrokes): <ALT><SPACE>x or if you are being extra careful: Text Type (Simulate Keystrokes): <ALT><SPACE> Delay: 100 millisecondsText Type (Simulate Keystrokes): x Quote Link to comment Share on other sites More sharing options...
terrypin Posted August 25, 2015 Author Report Share Posted August 25, 2015 Thanks Alan. I think you're probably right. What I did was to add a restore command before the maximise: Window Restore: <Current Window>Window Maximize: <Current Window> So far that invalid state hasn't reoccurred, although it's so rare and unpredictable that I'm not sure if that fix will always work. I'm also wondering if this extra delay I've added after the above is significant. Delay: 0.3 seconds Of course, it would help if we could come up with a reliable way of producing this state. I'm almost sure I've not seen it except when running a macro. So I'll ask Support for any, er, insights. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.