• Content count

  • Joined

  • Last visited

  • Days Won


terrypin last won the day on May 15

terrypin had the most liked content!

Community Reputation

2 Neutral

About terrypin

  • Rank

Contact Methods

  • ICQ

Recent Profile Visitors

81 profile views
  1. Thanks acantor. I think the registry had somehow become corrupted. After deleting the main ISS section and rebooting etc, things are now OK. Appreciated your help. Terry, East Grinstead, UK
  2. In a more careful check of Preferences I found this setting which appeared to be what I'd missed. But using it caused further problems as follows. I ensured that the Sidebar was not displayed. Then I enabled Preferences > General > Misc > 'Save settings as defaults for all users' and clicked Apply. But as soon as I clicked OK, my main macro file FULL-2016.mex was suddenly closed and this empty macex.mex file appeared in its place. If I then re-opened FULL.mex, the Sidebar was back and I found that the above setting was again now disabled. Worse, I'm now unable to close that macex.mex file. Terry, East Grinstead, UK
  3. So your sidebar doesn't appear automatically every time you start MX Explorer? That seems to imply there's a 'Save settings' option somewhere that I've missed. I'll take another look when back at my PC tomorrow. Terry, UK
  4. Have I overlooked a setting that will remove the Sidebar please? I appreciate it's only a few keystrokes to toggle it off/on, but I very rarely need it and I use the extra space it takes. If there is no setting, how about a hack? (I tried a simple macro activated by MX Explorer opening, but found it unreliable.) Terry, East Grinstead, UK
  5. @acantor The shortcut fails from the Desktop and the Start menu, its two limited locations. From my earlier googling I get the impression that program shortcut keys are inflexible and erratic in use and have concluded that they're best avoided. My fingers are not quite that inflexible! I was referring to your apparent recommendation to use four keys. ("But the safest combos are Ctrl + Shift + Alt + something.") Terry, East Grinstead, UK
  6. Thanks, but no Cortana problem here. BTW, I assume you did see my post (10:36 am yesterday) reporting success? Terry, East Grinstead, UK
  7. No change, still 8 secs before the TBD appears. Terry, East Grinstead, UK
  8. I'd say my initial estimate of 5 seconds was too short. The following macro, which opens a specific workbook in Excel 365, cannot continue processing for at least 8 seconds after activation. The file is loaded very quickly, but as rberg suggested in his 30th April post MX Pro then waits a long time. Program Launch: "20160724-Day03-Hoops-Clovelly-J-e570-m6.6.xlsm"" (Normal) Parameters: Text Box Display: Test // It takes about 8 seconds before text box appears. IOW, before macro can continue. However, the good news is that if instead I use the Run box, as shown in the following macro, it can continue in about 2-3 seconds: Text Type (Simulate Keystrokes): <WIN>r Delay: 0.1 seconds Text Type (Simulate Keystrokes): excel.exe "C:\Users\terry\Dropbox\FinishedWalks\20160724-Day03-Hoops-Clovelly-J-e570-m6.6.xlsm" Delay: 0.1 seconds Text Type (Simulate Keystrokes): <ENTER> Delay: 0.5 seconds Wait for Window Title: xlsm - Excel // DISABLED. If included, the delay increases dramatically to a duration like the basic method. Text Box Display: Test I should have tried that approach earlier, especially as I've used it before for program launching. The article referenced in Cory's post yesterday reminded me about it. Note my comment about the negative effect of using the more logical command Wait for Window Title instead of a (trial/error) 0.5 s Delay. Terry, East Grinstead, UK
  9. My fingers must be less flexible than yours! But the three key options I tried all failed. Here's an example, in case there's an obvious mistake.
  10. Thanks Cory, I'll experiment with some of those.
  11. Yes, that's what I mean by 'access': MX Pro access to Excel to continue processing commands. IOW, I want to get the macro to do stuff in Excel as close as possible to the speed I can do so manually, including opening Excel and having it ready to work.
  12. Thanks, understood. That macro got no further than the Command Prompt window. Typing at the cursor "C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE" did then open Excel, although a further 6 seconds elapsed before the hour glass vanished and operations were accessible I'm no batch expert anyway, and I haven't tried running batch files on this WIn 10 Pro PC until now. But this simple one-line macro, echo The test works OK run directly by d-clicking it in its Explorer folder, failed to retain the message (assuming that's what flashed briefly). By adding a second line echo The test works OK Pause the command window stayed open: https://www.dropbox.com/s/raijri50ftvvfeo/UsingBatchFiles-01.jpg?dl=0 And substituting that batch instead of C:\Users\terry\Dropbox\BATCH\Excel-Run.bat where Excel-Run.bat is start "C:\Program Files (x86)\Microsoft Office\root\Office16\EXCEL.EXE" exit gave the same correct result, so I'm almost there. Even so, I'm not sure it will significantly improve access time to Excel. -------------------- Sun finally out in earnest this morning, so heading off for a 9 mile hike, but will get back on the case asap. Terry, East Grinstead, UK
  13. Thanks both, sorry for delay in replying; away for a while. Interesting ideas and will try harder later. Meanwhile I had a brief attempt but so far @acantor, Having trouble assigning a hotkey that works! I have rather few to choose from and thiose I've tried so far either do nothing (there's no feedback) or do something unexpected. @rberg: Do you mean launch the Command Prompt window? That I can do via Win + X. Terry, East Grinstead, UK
  14. Many thanks, appreciate your taking the trouble to test. That could well be the explanation but, if so, it does seem a very generous delay, considering that all that's been done is to open a file. I have another application, my video editor, Movie Edit Pro, that displays very similar behaviour - but worse, Immediately after it's started, there's a delay of nearly 10 seconds before it will let me even activate any macro!
  15. Thanks, but as per my reply to Cory there's no problem with launching Excel - it's immediate as I said in my opening post. By whatever method I use. It's the subsequent delay that I don't understand. As if Excel prevents MX Pro working for that long delay.