Hi,
actually try out status icons and have some questions:
- Why icons from .dis are not supported?
- Which sizes are used/recommended?
-
They have to be Windows icons, present in the system image list. So .ico files and .exe, .dll containers work but .dis icon sets won't.
-
Same as normal Windows icons, with the same multiple-size options and size selection and/or scaling at different DPIs. Usually the 16x16 image will be used at standard DPI, 32x32 image at 200% DPI, etc.
Good to know, iconsets should be supported. The advantage of a set is not having icons "lying around" in images. 
How do I enable the Status Icons feature?
If I right click on a folder, I don't see it.
I am watching the video and watching about Status Icons, and I don't have a context menu like in the video.
Just a standard Windows context menu.
By default the commands are in the Properties drop-down on the default toolbar. In Leo's video he has added the same commands to his Folder context menu using the File Types system.
OK.
The context menu items are actually part of the default config now, although I'd have to dig into the code to work out when/if they get added to existing configs.
If they're missing in your config, you can use the same commands from the toolbar menus in the context menus. When I get a moment I will update the thread in the Buttons area here about adding the labels to the context menus.
Yes, and it’s borring... 
Each time I switch to another language (often to translate Opus), items is add to the context menu (why between Cut and Copy items?).
(The blue items are add too)
Actually adding .dis support would've been handy, I also was surprised internal format is not supported. It is not possible or just not implemented?
Anything is possible, but Opus would have to extract the icons from the .dis file and turn them into real .ico files which it then kept track of, and most .dis icons are the wrong size and won't scale down with great quality, at least when considering standard DPI (scaling 22x22 -> 16x16 can look OK but usually not fantastic).
Creating special status icon sets supporting 16, 32,... should not be that problem. 
@leo
Well, I've already found the dedicated topic about the problem, with suggestions to split .dis into collection of .png - it works, so it does not seem to be a problem all in all, even if it works same way under the hood (i.e. DO extracts images and splits those according to xml, then stores extracted and used icons as .png files inside own icons folder).
Also, if it is implemented, icon-packs authors may start adding bigger/smaller images into their sets (it's no problem, whet you have source psd for example).
TBH we didn't really envisage that people would want to create hundreds of status icons, rather than a handful. If it's just 4 or 5 then having a few loose icons in a folder doesn't seem like an issue to me.
@leo
My point actually is not to get rid of separate icon files, but to have an option to bundle those matching the program icon set and have a nice'n'easy way to get those from .dis if anyone would like.
There is really no need in having hundreds of those in use or having DO handle system calls to those icons from xml-mapped zipped images in realtime. Just having DO able to extract those from .dis like from *.(exe|dll) would be enough, it they are stored as .png inside DO folders it would've been perfectly acceptable.
You could store the icons in a DLL file (sometimes renamed .ICL for Icon Library if it only contains icons and no code). This is common for normal icon libraries.
We didn't use standard DLL icon libraries for toolbar icon sets since the image sizes are incompatible and we needed extra metadata, but for status icons I don't see a downside to using them.
I just tested it by randomly adding the icons from 7zFM.exe and dopus.exe into an icon library and the resultant .ICL file works fine with Opus. Took about 10 seconds to do in Icon Workshop:
Could you post the ICL......
Regards, AB
It's the same icons you can get by pointing the icon picker at dopus.exe (or 7zFM.exe)