>> Versus
>>    1. User is in Library, status on side
>>    2. User goes to document, /t u twice to banish status
>>    3. User returns to library which STILL has status on side, simply
>> because it always does.  (I can't make it go away at any rate.)
>>    5. User goes to document... status is gone.
>
> I personally would like to implement this.  Indeed, I will unless someone
> objects.
>
> Except:  "On side?"  Are you working on a UX50?  I didn't know my
> fullscreen
> code worked on a UX50 at all.  It's nice to know.

Yep, using a UX50 with a 23-Dec snapshot build due to the full-screen
image-zoom problems in the November release.  Works pretty well; I'll have
to install a newer build to give you better updates but like I said I've
been working on other database issues.  (And deciding that SuperWaba isn't
mature enough or open-source enough to be worth supporting. <grimace>)

Of course while typing this I suddenly got a reset error in Plucker, but
that's been pretty rare.

The library never hides the status area, but does allow switching between
minimized and maximized well.  The docs allow all three modes but getting
to full-screen takes several <ctrl-t>u (/u) sequences.  So got no gripes
about it except the inability to hide the status permanently.
The wide-screen works
   -TMcN-
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev

Reply via email to