On Sun, Jan 13, 2002 at 11:19:36AM -0800, Sean 'Shaleh' Perry wrote:
> So, I was a E hacker way back when and saw the birth of Eterm. I even used to
> work with its author (ick).
You have my condolences. :) Eterm... bleah. So much required, for so
little gain.
> When Eterm was created it was realized that there is NO way to find out what
> the root looks like.
Seriously? That surprises me, since obviously screen grabber applications
can deal with the idea. Or do they go directly to the hardware display of
the image? I freely admit that I know pretty much nothing about
programming under X.
> So they made an app which sets an Atom that others apps (liek Eterm) can
> query.
The image is stored in the atom? Seems memory intensive. Or is there just
a pointer to it?
> Once Eterm's psuedo transparency became popular other people used the
> idea. So this is how xchat and other apps achieve the same thing. Note
> that same apps (xv) do not set this Atom which is why Eterm does not work
> with xv.
Hm, implying that either:
(1) all other root-setting applications are broken
- or -
(2) what Eterm/Esetroot do is non-standard
Which is it? ^_^
> aterm codes a fall back. If the Atom is not set, it sets its background
> to ParentRelative which mimics the root window. This however does not
> work as well.
So there is a way to find out the root bitmap, then? :)
> The proper solution is for bsetroot to properly set the Atoms that the
> transparent apps want.
What about bitmaps in general? We have bsetbg, which requires one of
display/Esetroot/xsri/xv, and it sounds like only Esetroot does things in
the right way.
--
Marc Wilson
[EMAIL PROTECTED]
[EMAIL PROTECTED]
