Thanks guys, I just recompiled everything from scratch and will see if the issue clears up; and report back.

It did dawn on me however; would it not be proper for the offending piece:

if (l->icon && (l->icon->h()+2)>hmax)

to be re-written as

if (l->icon->h()+2)>hmax && l->icon ) ?

I seem to recall most compilers will generate assembly from right to left, so technically it tries to check the icon height before testing if an icon exists. I noticed in other parts of FL_Browser, icon is always checked first before trying to access its elements.... just a thought.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.