It's more complicated than that, actually.
Further in the message there's a link to
screenshot showcasing wmaker's handling of icons
for the complex applications. On the shot, there
are icons for:
* LibreOffice's StartCenter: 5th icon from top,
window class as reported by Wmaker:
"VCLSalFrame.DocumentWindow.libreoffice-startcenter"
* LibreOffice's Writer: 7th icon from top,
window class:
"VCLSalFrame.DocumentWindow.LibreOffice 3.6"
* miniwindows for writer documents which were
open respectively 1st and 2nd in the LibreOffice
session: 2nd and 1st icons from the bottom.
These both are LO Writer windows with documents
open, but their window classes are different:
"VCLSalFrame.DocumentWindow.libreoffice-startcenter"
(2nd from bottom)
"VCLSalFrame.DocumentWindow.LibreOffice 3.6"
(1st from bottom).
In WMWindowAttributes, there are two entries, as
expected.
http://s1311.photobucket.com/user/georgius70/media/20140825_wmaker_different_libreoffice_icons_zpsd5af77bb.jpg.html
***
The issues are:
1) If I change the *appicon* for
"VCLSalFrame.DocumentWindow.LibreOffice 3.6",
the miniwindow icon (of the same class) stays as
it was. Conversely, if I change the miniwindow
icon, the app icon changes, too.
2) For some time, LibreOffice in-built icons
used by default for miniwindows are rendered
with errors, as seen on pic, the 1st icon from
bottom, at least in 3.6 series of LO.
***
The suggestions:
1) Is it possible to introduce handling for
miniwindows icons separated from respective app
icons? These are already treated specially in
wmaker, after all, and icons for them are
already being processed in slightly different
way (different dialogs, different behaviour).
2) Is it possible to introduce handling of the
miniwindows representations on base of window
class AND window title? By their nature
miniwindows are, as like as not, related to the
data files instances.
So, as to keep compatibility, why not have
WMWindowAttributes entries looking like
(comments explicate the concept some more)
/* the miniwindow for the fancy.odt is iconed
with "fancy icon.png" */
"VCLSalFrame.DocumentWindow.LibreOffice 3.6" = {
/* in the respective dialog, an additional
checkbox would be required */
IsMiniWindow = Yes;
/* additional field for the window title would
be required, too */
/* regexes or at least shell patterns would be
preferrable, if at all doable */
WindowTitle = "fancydocument.odt - *";
AlwaysUserIcon = Yes;
Icon = "fancy icon.png";
};
/* the miniwindows for all other document titles
are iconed with "openofficeorg3-writer.png" */
"VCLSalFrame.DocumentWindow.LibreOffice 3.6" = {
IsMiniWindow = Yes;
/* empty/blanks-only field value considered to
be all-matching */
WindowTitle = "";
AlwaysUserIcon = Yes;
Icon = "fancy icon.png";
};
/* traditional format, implicitly regarded as
pertaining to app icons only, not miniwindows */
"VCLSalFrame.DocumentWindow.LibreOffice 3.6" = {
AlwaysUserIcon = Yes;
Icon = "openofficeorg3-writer.png";
};
***
Well, what do you think? BTW, I do not consider
an attention to the icons handling to be
misdirected. E.g., personally, I'm relying quite
heavily on the visual cues from app and
miniwindow icons in my daily work.
Yury
--
To unsubscribe, send mail to [email protected].
