Livia Koch wrote:
> I'm not sure if I said correctly what I wanted...
> What I meant is for example in the function
> 
> void Fl_Group::insert(Fl_Widget &o, int index) {

[... code snipped ...]

> I can't get the value of index or of array_ (or any information about them).

I read this that your debugger doesn't find the symbols of the FLTK lib. 
Did you compile the FLTK lib with debug info? If yes, you must also link 
with the objects that have it, i.e. use e.g. <fltk-src-root>/fltk-config 
--ldflags etc. to link your program (or maybe it can work if you install 
the lib after compiling with debug). But probably you new that and you 
meant something else...

> It's of course obvious that outside the function I won't be able to get the 
> value of a variable that doesn't exist anymore...
> 
> About the number of widgets: as long as I have less than something around 
> 5000 widgets, it works fine. And then it starts acting weird, until it 
> finally gets damaged. I know it would be much more helpful if I had a small 
> compilable example I could post... I'm trying to write one.

 From your code example I can see that you're using FLTK 1, but I can't 
see if it is 1.1 or 1.3. If it's 1.1 then the coordinate space in 
Fl_Scroll is limited to (signed) short, i.e. +/- 32767. Could this be 
the cause of it "acting weird"? What does it do when it is acting weird?

However, this would *not* explain the described crash in fl_throw_focus.

A suggestion just for testing: if you're using fltk 1.1, you could try 
to use fltk 1.3 instead. It is API compatible with a few exceptions (one 
regarding Fl_Scroll). You'd get two advantages:

(1) the coordinate space has changed to full int (32 bit in most cases)

(2) *if* you deleted widgets somewhere accidentally, *then* they would 
be removed from the containing group automatically, and then there 
shouldn't be the crash in throw_focus() any more.

But that probably wouldn't directly point to the potential bug elsewhere 
in the code, it's only intended as a testing aid.

Albrecht
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to