On 16.12.2011 18:42, Greg Ercolano wrote:
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
On 12/19/11 01:40, Albrecht Schlosser wrote:
Greg, what happens if you configure FLTK in these cases with
--disable-xdbe? Or did you? According to what Ian wrote, this
would be necessary to replicate the effect, if your system
used XDBE otherwise (the default).
Hadn't tried it.. I'll give
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
Don't know, I am using a Red Hat 5.5, 64 bits, through Exceed.
I will check tomorrow.
Exceed? Running on a Windows host? Hmm, I wonder if that's
the problem?
Have you tried another server (I like Xming much better
than Exceed on =
WIndows hosts these days, had all sorts of
OK, that's interesting.=20
(Though I guess it does not fully preclude the possibility that it is an
X-server issue, if there's some sort of weird 32/64 thing going on or...
Hmm...)
Anyway, does it exhibit the same misbehaviour run locally on the
machine? Is it only via Exceed that you
I have no local access.
OK - that's a pity, it will surely make diagnosis harder!
I don't have the bits to recreate your setup, so this is all going to be
guesswork and fishing.
Maybe someone clever will step up and fix it!
The problem happens on the Fl_Double_Window (probably due to
a
Might be worth trying with non-zero dimensions, just to see if that
makes any different here...
e.g. try;MyWin() : T(5,5,90,90) {}
Works fine.
A modified Fl_Double_Window.cxx works for me :
in void Fl_Double_Window::flush(int eraseoverlay) {
line 345-348 or near,
myi-other_xid is subsequently used in several places
without always
checking to see if it is NULL or not, so I worry that this
will throw
other issues.
I hope not in to much places because Fl_Double_Window::resize(...)
already put other_xid to 0 (marker for deletion)
I quickly
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 keep my patch until my tests are ok for a next fltk
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 curious: when you say there's no local access,
On 12/14/11 08:52, David FLEURY wrote:
Hi,
I am testing the tile sample for the distrib, and when resizing the tile
where the subwindow is, I have these errors (under linux) :
X_CreatePixmap: BadValue (integer parameter out of range for operation) 0x0
X_CopyArea: BadDrawable (invalid
I wouldn't think font size would affect that demo though, would it? I =
don't know.
Anyway, as another ref point, testing with ubuntu 11.10, all seems fine, =
no errors flagged.
I wonder if there's something odd about your graphics driver, or =
something?
Don't know, I am using a Red
On 14 Dec 2011, at 21:36, David FLEURY wrote:
I wouldn't think font size would affect that demo though, would it? I =
don't know.
Anyway, as another ref point, testing with ubuntu 11.10, all seems fine, =
no errors flagged.
I wonder if there's something odd about your graphics driver,
21 matches
Mail list logo
