Just curious: when you say there's no local access,
does this mean you're using a remote desktop,
or is the app running over a remote X display?
(export DISPLAY=someremote, etc)
remote display
Perhaps the messages are showing up when the tile size
approaches 0 in width or height, and this
After further tests, I have come to more Xlib Error on using Fl_Double_Window
in a tile resize to 0.
It seems that this is not the better to design a complex Window.
At this time, I just change the Fl_Widget::visible() to remove all my errors
(adding a check against w() and h() being positive)
On 15 Dec 2011, at 14:29, David FLEURY wrote:
Sorry, I should have said seevral places in the flush() method without
checking... though mostly to call the draw() method, so if draw() is
internally always checking that the xid is non-null it may well be
fine...!
Good. For now, I will
On 16 Dec 2011, at 04:18, Greg Ercolano wrote:
X_CreatePixmap: BadValue (integer parameter out of range for operation) 0x0
X_CopyArea: BadDrawable (invalid Pixmap or Window parameter) 0xa00043
X_FreePixmap: BadPixmap (invalid Pixmap parameter) 0xa00043
I have no local access.
Just
On 12/16/11 09:12, Ian MacArthur wrote:
[32bit vs 64bit observations]
Just to add some info to the mix: I tried a test between
two linux machines:
1) fedora 3 32bit/Xorg 6.8.1 (2004)/flwm
2) centos 5.5 64bit/Xorg 7.1.1 (2006)/flwm
I
OK, though I still think there should be a Better Way!
This is why I posted ;)
[...]
Sorry, what I meant was that when you are using an X-server (Exceed or
otherwise) to run the apps on a Linux host, but displaying on a Windows
host (which was the configuration you described initially)
[...]
A related question might be why the 32-bit linux works whilst the 64-bit =
does not, but that may well be some subtle difference in the way the X =
client code on the 32/64 bit versions behaves.
Hum, probably not a 32/64 bits issues.
I have no dev package available for RedHat 5.5
[...]
A related question might be why the 32-bit linux works whilst the 64-bit =
does not, but that may well be some subtle difference in the way the X =
client code on the 32/64 bit versions behaves.
May be not a 32/64 bits issues.
I have no dev package available for RedHat 5.5 (32bits), so
On 12/16/11 09:12, Ian MacArthur wrote:
[32bit vs 64bit observations]
Just to add some info to the mix: I tried a test between
two linux machines:
1) fedora 3 32bit/Xorg 6.8.1 (2004)/flwm
2) centos 5.5 64bit/Xorg 7.1.1 (2006)/flwm
I have the
I wouldn't derive from Fl_Window, as that implies your
coordinate space origin gets reset to zero. Changed that
to Fl_Group.
Also, fixed your yellow borders a bit; your code wasn't
consistent with the +1/-1 offsets to keep the border onscreen.
Greg,
Thank you
On 12/16/11 00:07, Robert Strickland wrote:
Thank you so much for your help. Changing from Fl_Window to Fl_Group did the
trick. I don't think I would have figured this out on my own.
Your FLTK Cheat pages are a tremendous resource. Thanks for creating and
posting them. Without them, I
11 matches
Mail list logo
