William F Pokorny <ano### [at] anonymousorg> wrote:
> What I'm testing is what the nice, verbose error message from X
> suggested - XInitThreads. This seems to add lock / unlocks around all
> the x11 interactions. Thus far, it's working(1).
> (1) - The other x11 issues routinely seen OK too - so far.
that man page merits close reading. it only speaks about 'Xlib', the "client
library", not (the underlying) X (server). another pertinent man page, re the
event/interrupt issues snipped from below, is 'XIfEvent(3)'. my understanding
(from somewhat dim, 20+ years old memory) is that whenever the window "object"
is accessed, you'll need some kind of mutex/XLockDisplay guard arrangement,
another "rant" re "nice, verbose error message". a few days ago, in an email,
needed to ask what the person (also an Ubuntu user, as it happens) got in reply
when executing "$ which badname", since "badname" did not seem to work. answer:
"nothing (an empty line)". the default behaviour for 'which' is to print (to
stderr) a message like "which: no badname in ($PATH)". what I do not understand
is why the Ubuntu maintainers expend "man-hours"/time + effort on making s/ware
_less_ informative, and therefore less valuable, to the user. (it sort of
boggles the mind, and that's before the "conspiracy" paranoia kicks in! :-))
> Aside: An idea on my 'maybe someday' wish list is POV-Ray run-able in a
> continuous loop(2) while accepting scene updating input. Re-reading and
> rendering a scene file as edits/updates are made. I think it possible to
> do limited modeling (spline editing say) without jumping up to Blender,
> Moray or whatever tool to do it.
a "hacked" Tclsh?! ;-) like the idea though, to be able to interactively build
up scenes would be way cool.
Post a reply to this message