View Single Post
Old 02-19-2012, 11:25 AM   #13
Nyoxi
Connoisseur
Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.Nyoxi can really shake a tail feather.
 
Posts: 55
Karma: 116549
Join Date: Jan 2012
Device: Kindle Touch
Quote:
Originally Posted by bhaak View Post
Just a small FYI, you can test out different window title by using xev, for example "xev -name L:A_N:application_ID:x11xev".
That's a nice tip bhaak.

Since it seems that this is interesting to more people I will share again the few things I have learend recently (since my new post).

Chrome layer contains the searchbar on top and ads on bottom (for SO version).
Window title is contained in special window called titlebar.
Titlebar is normaly on chrome layer.
If PC:N titlebar behaves like a chrome (e.g. hides when chrome hides). (TODO: find
out when chrome hides and if it's of any use)

params:
Code:
L   str  layer
N   str  window type: "application", "dialog", "pillowAlert", ...
ID  str  name of the window or the parent window for dialogs
         "system" is reserved for system stuff
PC  str  "N" - set size to full screen
         "TS" - size to show chrome layer
         other or missing - normal window, size so that title bar is visible
         valid for L:A only
M   bool modal dialog window
         valid for L:D only
RC  bool round corners of the window
RKB bool requires KB -- positioned so as to expect showing keyboard
         valid for L:D only
bool value is expected to be: "true"/"false"
Nyoxi is offline   Reply With Quote