On Tue, 18 Jul 2006 23:58:08 +0200,
Kim Woelders <[EMAIL PROTECTED]> wrote:
Thanks a lot for your explanation.
| Yasufumi Haga wrote:
| > Hi all
| >
| > I'm trying to update ja.po file in e16.8.2, and I have an
| > uncertain entry in the file:
| >
| > #: src/backgrounds.c:2271
| > msgid "Enable background transparency compatibility mode"
| > msgstr ""
| >
| > Does "compatibility mode" in this entry mean the
| > compatibility with clients before 0.16.8 ?
| >
| No. It has to do with the pseudotransparency (PT) hint (_XROOTPMAP_ID)
| used by apps that do PT stuff.
|
| When "background transparency compatibility mode" is disabled (default)
| there is no change wrt. earlier e16 versions.
| Most PT apps (Eterm afaik being the only exception) use the background
| pixmap reported on the root window (i.e. the first desk), regardless of
| virtual roots, i.e. PT apps use the wrong background image when not on
| the first desktop.
| There have been countless questions about this issue over time.
|
| When "background transparency compatibility mode" is enabled the
| background pixmap of the *current* desk is reported on the root window,
| which makes most PT apps seem to behave properly in most situations. The
| cost is unnecessary PT ops in apps that should not be affected when
| switching desks.
Let me summarize it briefly :)
PT function used by usual apps except Eterm is always using the image
of the first desktop, and this means a wrong background (i.e. the image
of the fisrt desktop) would be shown when the app is placed in a desktop
other than the first desktop.
That's why "background transparency compatibility mode" is introduced
in e16 to fix this issue. If you enable this mode, PT apps use the image
of the desktop where they are placed NOW as a background.
Even if they are in a differect desktop than the first, PT works normally
as expected with this mode. This also implies that even if you enable this
mode, you can't see the difference, or the effect of the mode unless you
are using a PT app except Eterm.
I hope this is correct :)
| The term "background transparency compatibility mode" is probably not
| very well chosen, suggestions for a better one are welcome :)
| The compatibility in question was in my mind compatibility with every PT
| app other than Eterm (which behaves properly in any case).
What about "adjusted (pseudo)transparency mode", I mean the mode
adjusted to the PT function of apps so that it works correctly?
or,...well..."every-PT-app-get-happy mode" (sorry, just a joke)
---
"Thank you for telling me the truth." --- HAL9000 in "2010"
Yasufumi Haga [EMAIL PROTECTED]
http://homepage3.nifty.com/peterpan/
fingerprint:0EFA 299A BC32 7D68 1FEF BA2B 804E 9B15 C4F0 F9F0
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users
