LOGIN / SIGN UP

#166 Autoproperty Layer not working in combination with autoproperty Focusable=false

Reported by: cynan Assigned to: ioerror
Phase: release-0.1.10 Component: autoproperties
Type: bug Status: closed
Priority: 3: Medium
Watchers:

Attachments

Description

I have this line in autoproperties:

Property = "^xterm,^myclass" { ApplyOn = "Start New Reload"; Focusable ="False"; Layer = "AboveHarbour" }

Initially, the xterm (with class name "myclass") is above other window, after focusing on the second window the xterm falls under it, although the xterm is in higher layer. It works properly when the property "Focusable=false" is deleted.

I have detected this fault in release-0.1.9 (maybe already in 0.1.8). It is ok in 0.1.7. I have Debian Lenny.

2009-04-12

19ioerror
15:12:44 changed from new to closed
15:12:36

Patch is in git. Please report if it breaks anything.

2009-03-10

118709a09b21f57f64f575d542f83533?s=24cynan
00:41:17

It works fine. Thank you very much.

2009-03-09

19ioerror
21:11:48 attached fixLayerAndFocusable_1.diff
21:11:00

Thank you for the bisect, it's really helpful. I think the problem is caused by an if-clause added in 5ce58a637. Please try the attached patch on git HEAD.

118709a09b21f57f64f575d542f83533?s=24cynan
16:19:25

I used git bisect first time so I hope that in right way. After iteration it wrote "5ce58a637bc158327ddd6a019194bfe9f83f9850 is first bad commit".

To be unfocusable - I do not want this xterm in "MRU Windows" menu. I need information about the actual number of workspace so I have minisized xterm with this number in corner always above. I know, it is dirty way, but it was easy for me to do that.

2009-03-08

19ioerror
21:51:57

Would you be so kind as to do a git bisect on this? And out of curiosity, why do you want a xterm to be unfocusable?