Fwd: .icewm/winoptions attributes setting help

Hi Adam,

To use winoptions you most know the WM_CLASS(STRING) of the software. If you
use xprop over xclock you will see something like this:

==========
_NET_WM_PID(CARDINAL) = 1611
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
_ICEWM_TRAY(CARDINAL) = 0
_WIN_LAYER(CARDINAL) = 4
_NET_WM_DESKTOP(CARDINAL) = 0
_WIN_WORKSPACE(CARDINAL) = 0
WM_STATE(WM_STATE):
                window state: Normal
                icon window: 0x0
_NET_WM_STATE(ATOM) =
_WIN_STATE(CARDINAL) = 0, 63
WM_CLIENT_LEADER(WINDOW): window id # 0x1a0000a
WM_LOCALE_NAME(STRING) = "es_CL.UTF8"
WM_CLASS(STRING) = "xclock", "XClock"
WM_HINTS(WM_HINTS):
                Client accepts input or input focus: False
                Initial state is Normal State.
                bitmap id # to use for icon: 0x1a00001
                bitmap id # of mask for icon: 0x1a00003
WM_NORMAL_HINTS(WM_SIZE_HINTS):
                program specified size: 164 by 164
                window gravity: NorthWest
WM_CLIENT_MACHINE(STRING) = "OS-Home"
WM_COMMAND(STRING) = { "xclock" }
WM_ICON_NAME(STRING) = "xclock"
WM_NAME(STRING) = "xclock"

=====

The WM_CLASS(STRING) in "xclock", "XClock". Then, in your winoption, you
must write:

xclock.XClock.layer: OnTop
xclock.XClock.allWorkspaces: 1
xclock.XClock.ignoreWinList: 1
xclock.XClock.ignoreQuickSwitch: 1
xclock.XClock.fMove: 0
xclock.XClock.fResize: 0
xclock.XClock.fClose: 0
xclock.XClock.fMinimize: 0
xclock.XClock.fMaximize: 0
xclock.XClock.fHide: 0
xclock.XClock.dTitleBar: 0
xclock.XClock..dBorder: 0


2010/9/14 Maulis Adam <[email protected]>

> Hi,
>
> here is the part of my ~/.icewm/winoptions:
>
> XClock.systemclock.layer: OnTop
> XClock.systemclock.allWorkspaces: 1
> XClock.systemclock.ignoreWinList: 1
> XClock.systemclock.ignoreQuickSwitch: 1
> XClock.systemclock.fMove: 0
> XClock.systemclock.fResize: 0
> XClock.systemclock.fClose: 0
> XClock.systemclock.fMinimize: 0
> XClock.systemclock.fMaximize: 0
> XClock.systemclock.fHide: 0
> XClock.systemclock.dTitleBar: 0
> XClock.systemclock.dBorder: 0
>
> These options does not work. The clock still resizeable and so.
>
> Thanks for your help!
>
> Adam Maulis
>


-- 
Miguel Pedreros.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

_______________________________________________
IceWM-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/icewm-user