Before I continue I should say I am running FLTK 1.3 on Ubuntu 10.10. I am building it like so:
g++ -o dnd_broke dnd_test.cpp -g -L/usr/local/lib -lfltk_gl -lGLU -lGL -lfltk -lXft -lfontconfig -lpthread -ldl -lm -lX11 > Well, there is somnething about over-riding the resize() method of the > Rx window. Yes indeed. If you get rid of that call them I'm ok. It uses the underlying resize code. That was the big reason I wanted to come to terms with that code; I might have needed to add some housekeeping. It doesn't appear to be so obvious though, so I am starting to doubt that--I'd assume somebody would call me out for missing some essential call in there for overriding resize(). > Now, that kind of works, but the window frame gets drawn at the "full" > size but the contents are redrawn clamped to to 200 width. Something I can try later when I have a little more time is to adjust everything like I need to in resize and then just calling the underlying resize too. It should theoretically do nothing to the coordinates of anything but it might do the requisite housekeeping. I am a little bit afraid of performance though since the charts I'm drawing are pretty busy GL windows and I was hoping the window resize could have them adjust those charts in real-time (oooh pretty). > Yup - size_range() seems like it might work without the need for the > resize() method, but of course it only applies to top-level windows, A built-in clamp function would be useful to me, but not size_range. I wanted to clamp the heights of the boxes, but that was it. So if there's some stuff I can do to inform the toolkit to allow some components to scale and others to stay fixed, then I could resort to that. It would also get rid of some rather ugly code. I'm also considering the alternative of implementing my own internalized drag and drop. The data I'm trying to drag and drop is some more chart information. I am passing along the raw address to that data, and it's real clunky. When I drop to the desktop, I am sending rogue text files there with the address in them. I'd also get random compiler editors because I was accidentally dropping the addresses into my editor. So I might not want a real system-wide drag and drop here. That's not to say I won't want to import and export some data later. But anyways since I smelled it first I'll try any suggestions to make it work right. I hope to have some words tonight about what might have worked for resize(). _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
