• Glacial Cursor or Working Macros: Choose 1?

    Home » Forums » AskWoody support » Microsoft Office by version » Office 365 and Click-to-Run » Glacial Cursor or Working Macros: Choose 1?

    Author
    Topic
    #2379321

    Using Office 365, Win 10 Professional, fully updated, with add-ins Mendeley and Mathtype. Everything seems to work — except for one, fairly basic function that acts glacially. Want to go from one place to another using the mouse? Point, Click, There. Want to go using the arrow keys? Sorry — 2 characters per second is as fast as it moves, or 2 lines per second. So I went to Microsoft on-line help, finally got connected to a human, gave him control of my computer, and a few clicks by him solved the slow cursor problem — by turning off all macros i.e. killing Mathtype! Has anyone else seen this? Is there a work-around where one can use macros in Office 365 without having the cursor act lethargic? Thanks!

    Viewing 1 reply thread
    Author
    Replies
    • #2379338

      So I went to Microsoft on-line help, finally got connected to a human, gave him control of my computer,

      Never ever give anyone remote control of your PC, human or not. You never know who is behind the remote keyboard. That’s include ‘Microsoft’ support.

      • #2379366

        When the site says “Microsoft” and it’s a hotlink to a Microsoft address (not just overtly, but also with the mouse hovering over the link) and there’s been a bunch of conversation that shows someone asking the right questions, I thought it was a risk worth taking. It’s just like taking a machine to be repaired at the local shop; at times, one has to trust other humans or one is hamstrung. We trust the AskWoody folks for advice based on experience. Similarly, if one is actively seeking advice from the people who wrote the blinkin’ software, what option is there? My sense was that the person was unsure if their idea would fix what was broken and was doing down a checklist.  It was only after I couldn’t get MathType to work that I realized they’d incapacitated Macros.

    • #2379340

      In order to increase performance, I strongly suggest to try turning off “Windows animations” in:
      Ease of Access settings > Display from the column on the left.
      On the right, scroll down to the Simply and personalise Windows section

      Turn off the toggle named Windows Animations.

      That “Windows animations” affect Office 365 behavior. For example if you select different cell by pressing arrow key, it makes the selection go *ehrm* “nicely andsmooooth”. But also when running macro it slows your PC significantly. Another example of bul$&#*t added just to look cool, but fuctionality is suspended. This option should be OFF in default state, not ON, but Microsoft decided the other way.

      The small question on the end is, if your add-ons do use method Worksheet_Change or other methods, that can be “computing on the background”.

      Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

      HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

      PRUSA i3 MK3S+

      • #2379365

        Thanks. I flicked the switch, nothing changed immediately, and I suspect I’ll need to reboot to see the effect. I never would have found that without your help.

        • #2379519

          The truth is, that this may not solve your issue completely, but it definately improves working with macroes.
          I mean in the stage of debugging, you may want to higlight cells and see what happening on the sheet. At that stage, animations are not welcome.
          TBH, I dont need animations. I need productivity, not the beauty 🙂

          Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

          HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

          PRUSA i3 MK3S+

    Viewing 1 reply thread
    Reply To: Glacial Cursor or Working Macros: Choose 1?

    You can use BBCodes to format your content.
    Your account can't use all available BBCodes, they will be stripped before saving.

    Your information: