Greentext

8195 readers

1410 users here now

This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.

Be warned:

Anon is often crazy.
Anon is often depressed.
Anon frequently shares thoughts that are immature, offensive, or incomprehensible.

If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.

founded 2 years ago

MODERATORS

Early_To_Risa@sh.itjust.works

746

Anon goes back to Windows 10 (sh.itjust.works)

submitted 1 day ago by Early_To_Risa@sh.itjust.works to c/greentext@sh.itjust.works

146 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] BCsven@lemmy.ca 2 points 1 day ago (1 children)

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 1 points 1 day ago (1 children)

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 1 points 1 day 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.