Hi!
the component FvwmIdent very often (and sporadically) disappears
when I change the focus to other applications, start new applications
or change to other viewports (pages) or dekstops.
Compared with FvwmPager, the behaviour of FvwmIdent is much more
unstable. FvwmIdent windows just do not
On Thu, Jan 05, 2012 at 12:10:14PM +0100, Michael Großer wrote:
Does anyone know about this behaviour of FvwmIdent?
Is the reason known why FvwmIdent is that much damageable?
It's designed to work this way.
Look at the code:
case KeyRelease:
if (is_key_pressed)
{
Thomas Adam wrote:
On Thu, Jan 05, 2012 at 12:10:14PM +0100, Michael Großer wrote:
Does anyone know about this behaviour of FvwmIdent?
Is the reason known why FvwmIdent is that much damageable?
It's designed to work this way.
Look at the code:
case KeyRelease:
if
On Thu, Jan 05, 2012 at 10:43:23PM +0100, Michael Großer wrote:
When I additionally I set a StaysOnTop style to bring FvwmIdent on top,
I noticed that this does only work when I apply FvwmIdent on
xterms, but not on nedit, Iceweasel, FvwmIdent or some other instances.
Look at the MinimalLayer
Thomas Adam wrote:
On Thu, Jan 05, 2012 at 10:43:23PM +0100, Michael Großer wrote:
When I additionally I set a StaysOnTop style to bring FvwmIdent on top,
I noticed that this does only work when I apply FvwmIdent on
xterms, but not on nedit, Iceweasel, FvwmIdent or some other instances.
On Fri, Jan 06, 2012 at 12:02:47AM +0100, Michael Großer wrote:
Thomas Adam wrote:
On Thu, Jan 05, 2012 at 10:43:23PM +0100, Michael Großer wrote:
When I additionally I set a StaysOnTop style to bring FvwmIdent on top,
I noticed that this does only work when I apply FvwmIdent on
xterms,
On Thu, Jan 05, 2012 at 11:17:18PM +, Thomas Adam wrote:
On Fri, Jan 06, 2012 at 12:02:47AM +0100, Michael Großer wrote:
Thomas Adam wrote:
On Thu, Jan 05, 2012 at 10:43:23PM +0100, Michael Großer wrote:
When I additionally I set a StaysOnTop style to bring FvwmIdent on top,
I