1.7.161 report

Donald A. Peterson (donald@nd.edu)
Thu, 6 Jan 2000 09:58:59 -0500 (EST)


I really have not seen any important or blatant problems with this version
and I have been runing it for a week now (since Dec 30).  I only have
nitpicks. ;-P    The errors below are what get directed to stderr, I
don't really see any functional problems.

1) Upon closing any Wharf, I get a lot of X errors: viz.

X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  4 (X_DestroyWindow)
  Resource id in failed request:  0x4400001
  Serial number of failed request:  1501
  Current serial number in output stream:  1504
X Error of failed request:  BadDrawable (invalid Pixmap or Window
parameter)
  Major opcode of failed request:  62 (X_CopyArea)
  Resource id in failed request:  0x3c00006
  Serial number of failed request:  1266
  Current serial number in output stream:  1269

They always appear in pairs of opcodes 4,62 and usually 3 or 4 at a time.

2) Another Wharf issue is that the _first_ Wharf started in a session
reports several X Errors (Actually 1 per swallowed app, I believe):
XWharf: X Error
        Request 2, Error 3 0, Type: 0
XWharf: X Error
        Request 7, Error 3 0, Type: 0
XWharf: X Error
        Request 8, Error 3 0, Type: 0
XWharf: X Error
        Request 28, Error 3 0, Type: 0
XWharf: X Error
        Request 28, Error 3 0, Type: 0
XWharf: X Error
        Request 28, Error 3 0, Type: 0
XWharf: X Error
        Request 28, Error 3 0, Type: 0
XWharf: X Error
        Request 14, Error 9 0, Type: 0
XWharf: X Error
        Request 12, Error 3 0, Type: 0

However, if I stop the module and then start it again, no errors are
reported.  Odd. I can post the relevant portion of my ~GLA/wharf if it's
useful/interesting to the developers, but I'll save space here.

3)  Another possible Wharf thing.  Around 1.7.152 aspostit stopped being
swallowed nicely.  It now reports "Error: Shell widget PostItNote has zero
width and/or height" and I have an empty panel in the Wharf.  If I start
aspostit alone from the command line, it works just fine.  I have
recompiled aspostit just for good measure to no avail.  Any ideas?


That's it for "errors".  I really like the way theme handling is
done---obviously some good thought went into it.  Being able to just keep
a gzipped theme tarball and select a theme from the startmenu is
GREAT!  If I may make a suggestion for the theme handling, though, it
would be _really_ nice if the background image was loaded to the
background of the desktop you're on when you select the theme as opposed
to always changing desktop 0.  I honestly don't know how hard this would
be to integrate.

As I said, only nitpicky stuff.  This is really a fine version and I say
go for a 1.8!

Thanks for all the great work!
-Don
________________________________________________________
Donald A. Peterson	 | DPETERSO@.ND.EDU
Department of Physics	 | http://www.nd.edu/~dpeterso
University of Notre Dame | (219) 631-7716
--------------------------------------------------------

--
This is the mailing list for the AfterStep Window Manager for X.  To
unsubscribe, type the following command at the prompt 'mail -s unsubscribe
as-users-request@afterstep.org'.  For more help on AfterStep, refer to the
on-line documentation at http://www.afterstep.org.