I'm aware there are issues with cloud service icon overlays but is this being looked at? Files in the Google Drive directory have their icons sometimes disappear. Exiting Dopus and re-starting gets them back. This hasn't been an issue with Dropbox.
The issue seems to be with the Google Drive shell extension. (Opus does not treat it any differently to the shell extensions for Dropbox or other things which work OK.)
(Unless you have so many overlay shell extensions in use that the limit is being reached. Windows only allows for 15 overlay icons per process, and whichever are loaded first win. So exiting the process and then showing a Google Drive folder may let it establish its overlay icons, at the cost to some other extension of not being able to establish its own, if the limit is reached again.)
We are not looking into this as there's nothing for us to look into. Opus just asks for the icon + overlay via a Windows API, and the rest is up to Windows and the relevant shell extensions, which function as a black box as far as Opus is concerned. We could not look into this without Google's source code; only Google could look into it.
I was having this issue myself.
Is Opus at the mercy of this Windows Explorer setting?
Do tabs in Opus have their own process? Does Opus support hyperthreading?
It usually doesn't make sense to necro a decade old thread. 
So many things have changed since then. Google Drive isn't even the same thing as it was 10 years ago.
No, it has no effect on Opus.
No, all tabs live within the same process.
The question doesn't make sense. Hyperthreading is a CPU feature, not something software like Opus gets involved with.
Opus is multi-threaded, if that's what you meant to ask.
It doesn't make sense to keep it SEO searchable if the info is outdated and therefore incorrect, either.
I've been choosing old threads to stay on topic. Google Drive being different now is exactly the reason to ask new questions about it.
When I google search a topic and this is the one that is the best match, then the next person who googles the same issue will end up finding this updated info.
Yes that's what I asked.
Thank you for the info.
Please be realistic, for god's sake.
1 Like
*God.
I'm really not trying to do anything wrong.
If you want me to leave old threads alone, then I will.
Oh I see. That makes sense.
I don't really care about the timestamp on any particular information. I just need the info when I need it, as everyone else does.
In this case Leo had referenced "15 context menu objects" before Windows maxes out per process.
So I started to wonder if I should trim my context menu to less than 15 items, or if "process" and "thread" are the same things, and if lister tabs play a part in this.
Because in FL Studio you can 'detach' a plugin and it becomes its own process apart from FL Studio, and is delegated to any empty or low utilized cpu threads. I didn't know how it works with Opus.
I was just trying to append to the context already established in this thread, so that Leo doesn't have to repeat himself. Your share method is a good solution, thank you.