Re: assertion error "PRI(owl) >= priority" otp.c line 248

Rhialto <[email protected]> Thu, 11 Jul 2019 20:15:36 +0200

Newsgroups	gmane.comp.window-managers.ctwm
Message-ID	<[email protected]>

On Wed 10 Jul 2019 at 21:31:45 -0500, Matthew D. Fuller wrote:
> On Wed, Jul 10, 2019 at 10:28:15PM +0200 I heard the voice of
> Rhialto, and lo! it spake thus:
> > 
> > [...] None of the patches attempting to fix these bugs.
> 
> Hm.  I read this as "none of the patches fixed these bugs", but now I
> think it means "I didn't try it patched".  Is that right?

Sorry, yes that is what I meant.

> So, updated patch attached; as far as I can tell, this (and the
> previous variant) should fix that crash, and if that's also your
> historic one, should cleanse the world.

Indeed, I can't reproduce it anymore now with this scenario. I'm pretty
sure it is the same bug that happened "randomly" before.

I do notice that SetFocus() duplicates a lot of work that the FocusIn
and FocusOut event handlers do. I was wondering if SetFocus() shouldn't
just call XSetInputFocus() like it does now, but nothing else. Events
should come in and get the same code executed.

So I quickly tried it and it didn't exactly work out as expected. Even
though the events do arrive (according to xev), the
FocusVisualAttributes are not Set when I warp from one window to another
(i.e. the window frames are not updated).

But this is probably just a distracting side-track :-)

-Olaf.
-- 
___ Olaf 'Rhialto' Seibert  -- "What good is a Ring of Power
\X/ rhialto/at/falu.nl      -- if you're unable...to Speak." - Agent Elrond

signature.asc (application/pgp-signature, 455 B)