Help on heads again

[Jeremy Hankins]

Does current-head work for windows outside of the current viewport?

To test:

 - Create a couple of windows with unique names (e.g., via xterm -title
   "Foo" and -title "Bar")  Make sure that they're in different heads.

 - In sawfish-client run: (current-head (get-window-by-name "Foo")), and
   the same thing for "Bar".  You'll get the head ID of the head with
   the window.

 - Go to another viewport and fire up sawfish-client, run the same
   commands as before.  Does the output match, or did switching
   viewports change the head IDs?

Thanks!

--
Jeremy Hankins <nowan@...>

[Janek Kozicki]

Jeremy Hankins said:     (by the date of Tue, 20 Oct 2009 16:41:31 -0500)

> Does current-head work for windows outside of the current viewport?
> To test:
>  - Create a couple of windows with unique names (e.g., via xterm -title
>    "Foo" and -title "Bar")  Make sure that they're in different heads.
>  - In sawfish-client run: (current-head (get-window-by-name "Foo")), and
>    the same thing for "Bar".  You'll get the head ID of the head with
>    the window.
>  - Go to another viewport and fire up sawfish-client, run the same
>    commands as before.  Does the output match, or did switching
>    viewports change the head IDs?
> --
> Jeremy Hankins <nowan@...>
>

I just connectted a 3rd LCD, I have now 1600x1200, 1920x1200, 1600x1200.
I'll try to find time on Friday evening and test your stuff.

If you have any more explanations about what to test, or what to type
in sawfish-client, don't hesitate to write.

best regards
--
Janek Kozicki                                                         |

[Janek Kozicki]

Janek Kozicki said:     (by the date of Wed, 21 Oct 2009 19:27:59 +0200)

> Jeremy Hankins said:     (by the date of Tue, 20 Oct 2009 16:41:31 -0500)
> > Does current-head work for windows outside of the current viewport?
> > To test:
> >  - Create a couple of windows with unique names (e.g., via xterm -title
> >    "Foo" and -title "Bar")  Make sure that they're in different heads.
> >  - In sawfish-client run: (current-head (get-window-by-name "Foo")), and
> >    the same thing for "Bar".  You'll get the head ID of the head with
> >    the window.
> >  - Go to another viewport and fire up sawfish-client, run the same
> >    commands as before.  Does the output match, or did switching
> >    viewports change the head IDs?
>
> I just connectted a 3rd LCD, I have now 1600x1200, 1920x1200, 1600x1200.
> I'll try to find time on Friday evening and test your stuff.
>
> If you have any more explanations about what to test, or what to type
> in sawfish-client, don't hesitate to write.

One more thing - is it possible to test your patches on 1.5.0 ?

I'm afraid that I won't find enough time to upgrade to any later
version. Easier if I could just apply your patch to what I currently
have.


BTW: setting a useful config with three LCDs is a real PITA. I had to
downgrade xserver to 7.3, because the latest xorg is plain crashing
with more than one video card (when using xinerama), and this is a
well known bug. Xorg Devs say that it will stop crashing with 2.6.32. Well.

Also I can't have composite and xrandr anymore. Also due to two-card
problems. Even though 1st is NVS 290 & 2nd is NVS 280, and all NVS
nvidia cards are designed to cooperate with each other (a different
design than geforce or quadro). Weird stuff.

best regards
--
Janek Kozicki                                                         |

[Jeremy Hankins]

Janek Kozicki <janek_listy@...> writes:

> Janek Kozicki said:     (by the date of Wed, 21 Oct 2009 19:27:59 +0200)
>
>> Jeremy Hankins said:     (by the date of Tue, 20 Oct 2009 16:41:31 -0500)
>> > Does current-head work for windows outside of the current viewport?
>> > To test:
>> >  - Create a couple of windows with unique names (e.g., via xterm -title
>> >    "Foo" and -title "Bar")  Make sure that they're in different heads.
>> >  - In sawfish-client run: (current-head (get-window-by-name "Foo")), and
>> >    the same thing for "Bar".  You'll get the head ID of the head with
>> >    the window.
>> >  - Go to another viewport and fire up sawfish-client, run the same
>> >    commands as before.  Does the output match, or did switching
>> >    viewports change the head IDs?
>>
>> I just connectted a 3rd LCD, I have now 1600x1200, 1920x1200, 1600x1200.
>> I'll try to find time on Friday evening and test your stuff.
>>
>> If you have any more explanations about what to test, or what to type
>> in sawfish-client, don't hesitate to write.
>
>
> One more thing - is it possible to test your patches on 1.5.0 ?

Hmmm...  Possibly, I'm not sure how well they'd apply.  You could try,
if you want; it's these two commits on the git server:

52f6a8f667c6d5a354b13ba66d84624fe9456cc5
6071da522763e524d3a7ac6a061edb430d222161

> I'm afraid that I won't find enough time to upgrade to any later
> version. Easier if I could just apply your patch to what I currently
> have.

Even if they don't apply you can still run the test above, as that's not
dependent on my patches.

--
Jeremy Hankins <nowan@...>

[Flashrider]

Am Mittwoch, den 21.10.2009, 21:38 +0200 schrieb Janek Kozicki:

> Janek Kozicki said:     (by the date of Wed, 21 Oct 2009 19:27:59 +0200)
>
> > Jeremy Hankins said:     (by the date of Tue, 20 Oct 2009 16:41:31 -0500)
> > > Does current-head work for windows outside of the current viewport?
> > > To test:
> > >  - Create a couple of windows with unique names (e.g., via xterm -title
> > >    "Foo" and -title "Bar")  Make sure that they're in different heads.
> > >  - In sawfish-client run: (current-head (get-window-by-name "Foo")), and
> > >    the same thing for "Bar".  You'll get the head ID of the head with
> > >    the window.
> > >  - Go to another viewport and fire up sawfish-client, run the same
> > >    commands as before.  Does the output match, or did switching
> > >    viewports change the head IDs?
> >
> > I just connectted a 3rd LCD, I have now 1600x1200, 1920x1200, 1600x1200.
> > I'll try to find time on Friday evening and test your stuff.
> >
> > If you have any more explanations about what to test, or what to type
> > in sawfish-client, don't hesitate to write.
>
>
> One more thing - is it possible to test your patches on 1.5.0 ?
>
> I'm afraid that I won't find enough time to upgrade to any later
> version. Easier if I could just apply your patch to what I currently
> have.

well, I'm currently working (again) on my apt-repo, so if you're using
SID, you'll be able to grab a recent snapshot in some days.

>
> BTW: setting a useful config with three LCDs is a real PITA. I had to
> downgrade xserver to 7.3, because the latest xorg is plain crashing
> with more than one video card (when using xinerama), and this is a
> well known bug. Xorg Devs say that it will stop crashing with 2.6.32. Well.
>
> Also I can't have composite and xrandr anymore. Also due to two-card
> problems. Even though 1st is NVS 290 & 2nd is NVS 280, and all NVS
> nvidia cards are designed to cooperate with each other (a different
> design than geforce or quadro). Weird stuff.
>
> best regards

[Janek Kozicki]

Christopher Roy Bratusek said:     (by the date of Thu, 22 Oct 2009 22:04:53 +0200)

> well, I'm currently working (again) on my apt-repo, so if you're using
> SID, you'll be able to grab a recent snapshot in some days.

that would be awesome.

The only thing to make me happy is a valid deb-src repo.

--
Janek Kozicki                                                         |

[Flashrider]

Am Donnerstag, den 22.10.2009, 22:16 +0200 schrieb Janek Kozicki:
> Christopher Roy Bratusek said:     (by the date of Thu, 22 Oct 2009 22:04:53 +0200)
>
> > well, I'm currently working (again) on my apt-repo, so if you're using
> > SID, you'll be able to grab a recent snapshot in some days.
>
> that would be awesome.
>
> The only thing to make me happy is a valid deb-src repo.
>

mine would include i386 and src

[Janek Kozicki]

Jeremy Hankins said:     (by the date of Thu, 22 Oct 2009 08:12:42 -0500)

> Janek Kozicki <janek_listy@...> writes:
> > Janek Kozicki said:     (by the date of Wed, 21 Oct 2009 19:27:59 +0200)
> >
> >> Jeremy Hankins said:     (by the date of Tue, 20 Oct 2009 16:41:31 -0500)
> >> > Does current-head work for windows outside of the current viewport?
> >> > To test:
> >> >  - Create a couple of windows with unique names (e.g., via xterm -title
> >> >    "Foo" and -title "Bar")  Make sure that they're in different heads.
> >> >  - In sawfish-client run: (current-head (get-window-by-name "Foo")), and
> >> >    the same thing for "Bar".  You'll get the head ID of the head with
> >> >    the window.
> >> >  - Go to another viewport and fire up sawfish-client, run the same
> >> >    commands as before.  Does the output match, or did switching
> >> >    viewports change the head IDs?
> >>
> Even if they don't apply you can still run the test above, as that's not
> dependent on my patches.

OK, there you go (without your patches, currently):

I made three windows, called "1st" "2nd" and "3rd" respectively.

The results when in the same viewport:

user> (current-head (get-window-by-name "1st"))
0
user> (current-head (get-window-by-name "2nd"))
1
user> (current-head (get-window-by-name "3rd"))
2
user>

So it works when in the same viewport.



The results when in different viewport (I tried several different
viewports, in all 8 directions respectively to original one):

user> (current-head (get-window-by-name "1st"))
0
user> (current-head (get-window-by-name "2nd"))
0
user> (current-head (get-window-by-name "3rd"))
0

But then I moved all three windows to another viewport and did the
test again (from all 8 directions in other viewports):

user> (current-head (get-window-by-name "2nd"))
1
user> (current-head (get-window-by-name "3rd"))
1
user> (current-head (get-window-by-name "1st"))
1

Then I moved all the windows back to original viewport and tested
from all 8 directions:

user> (current-head (get-window-by-name "2nd"))
1
user> (current-head (get-window-by-name "3rd"))
1
user> (current-head (get-window-by-name "1st"))
0

It looks to be semi-random, when in different viewport.
Previously I had everywhere '0' at this point.


Did you ask for any other dual(triple:) head test, in any other
email, and I missed your post? I mean - do you want me to run more
such tests? :)

best regards
--
Janek Kozicki                                                         |

[Flashrider]

Am Freitag, den 23.10.2009, 06:43 +0200 schrieb Christopher Roy
Bratusek:

> Am Donnerstag, den 22.10.2009, 22:16 +0200 schrieb Janek Kozicki:
> > Christopher Roy Bratusek said:     (by the date of Thu, 22 Oct 2009 22:04:53 +0200)
> >
> > > well, I'm currently working (again) on my apt-repo, so if you're using
> > > SID, you'll be able to grab a recent snapshot in some days.
> >
> > that would be awesome.
> >
> > The only thing to make me happy is a valid deb-src repo.
> >
>
> mine would include i386 and src

I've just added debian/ scripts to librep, will do now for rep-gtk. and
perhaps for sawfish, too, if not, then tomorrow.

[Jeremy Hankins]

Janek Kozicki <janek_listy@...> writes:

> It looks to be semi-random, when in different viewport.  Previously I
> had everywhere '0' at this point.

Ok, that's kind of what I figured.  It would probable be a good idea to
change find-head (the function current-head is using) to return nil when
asked about a position outside of the viweport (i.e., a position not in
any head).  It looks like that's in src/functions.c, but I'm not certain
enough what's going on there to make that change myself (I haven't done
any C coding since '93).

> Did you ask for any other dual(triple:) head test, in any other
> email, and I missed your post? I mean - do you want me to run more
> such tests? :)

Not unless you can apply my patch and test that out.  I can send you a
patch against the current 1.6, if you could use that.

--
Jeremy Hankins <nowan@...>