• Hupf@feddit.org
    link
    fedilink
    arrow-up
    35
    ·
    1 day ago

    Of course opening the context menu takes its time. It’s gotta load a whole Electron framework first.

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      22 hours ago

      you just need a registry cleaner for that, dump out all the non-stock entries out of the list.

      • BCsven@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        22 hours ago

        It should cache those until your file extensions get a reg edit, there is no need to build the context menu fresh every time

        • rumba@lemmy.zip
          link
          fedilink
          English
          arrow-up
          1
          ·
          21 hours ago

          Ohh no, it’s not that it’s building the menu.

          Each one of those extra lines is a hook to a dll.

          rightclick potato.jpg

          imagemagic: what options should i give for potato.jpg loads image enough of imagemagic to tell antivirus: what options should i give potato.jpg loads enough of antivirus to tell

          Now if your apps are small or the context menu for them is will done, it’s hardly a blip But if you installed 27 different apps that want to be in the context menu and they’re all 100mb… that takes some time.

          • BCsven@lemmy.ca
            link
            fedilink
            arrow-up
            1
            ·
            20 hours ago

            Yeah so cache it so it doesn’t take time to show you the options. Once you click it can go do bullshit loading. We have a software that used to load and cache the dialogs at first boot and it was fast to use, now it builds the dialog at runtime and is slow to display the options. It sucks.