kohait00 Messages: 939 Registered: July 2009 Location: Germany
Experienced Contributor
hi there,
im having this problem, and can't an explanation for it.. any ideas what's wrong? the sizes of the head spacers seem to be misleading..
it changes sometimes when adding new stuff to application..
MatthiasG Messages: 27 Registered: January 2008 Location: Germany
Promising Member
hello,
i have seen something similar with the TabCtrls in my program. when compiled in debug mode the tab-headers are way too small. if i compile in optimal mode everything is fine though... couldn't find the source of this error till now though...
dolik.rce Messages: 1791 Registered: August 2008 Location: Czech Republic
Ultimate Contributor
Hi kohait
It doesn't look like a problem with springs, there are artifacts which are unrelated to springs (e.g. the height of menu bar)...
Is it reproducible? Did you try to compile on different machine or different options? Did you try full recompile (bomb button)? Could you post the code? (Or even better just a simplified example ).
if i run my program in debug mode, the font.Info().GetHeight() call returns 0. Running in Optimal mode returns 13.
Couldn't reproduce this problem in a simple testcase though, so i think the error is somewhere in my own code...
kohait00 Messages: 939 Registered: July 2009 Location: Germany
Experienced Contributor
same with me here, in OPTIMAL using MSC this thing just looks as expected, debug spews the problems..
EDIT: and one more: TDM GCC yields the same thing in debug mode. so it has to be on code side somewhere, depending on debug.
nlneilson Messages: 644 Registered: January 2010 Location: U.S. California. Mojave &...
Contributor
I had a similar issue as this.
In dlg.lay it looked OK.
When the app was run the EditField was about 6 times as high as it should have been, 3 up/down, that was white but the text was where it should be.
I just spent a bunch of time deleting that field, replacing, changing location, etc.. It just happened when it was in the third row down.
That was about 3 or 4 months ago, maybe the U++ update fixed it as there has been no problems since then.