GUI Editor bug
by Stefan Lundmark · in Torque Game Engine · 05/01/2004 (11:35 am) · 12 replies
I have been working with the GUI editor for a very long time now, it's great - but if you open the editor, putting an bitmap-object on relative position, pressing F10 to get back to see how it went, the object moves around 2 units to the right and 2 units up.
I have been able to reproduce this error every time I've tried to do the same thing. This is probably something that is known already, but I'd just like you to know.
I have been able to reproduce this error every time I've tried to do the same thing. This is probably something that is known already, but I'd just like you to know.
About the author
#2
I'm 100 % sure normal objects don't do this.
It seems to happen mostly in my play.gui though :/ not sure about this but I think so.
Imagine the normal healthbar object, with a hud on top of it.. everytime I use F10 the hud moves but the object stays intact.
Edit: Tried this on a clean build, same problem
05/02/2004 (7:20 am)
ONLY bitmap objects that use RELATIVE positioning.I'm 100 % sure normal objects don't do this.
It seems to happen mostly in my play.gui though :/ not sure about this but I think so.
Imagine the normal healthbar object, with a hud on top of it.. everytime I use F10 the hud moves but the object stays intact.
Edit: Tried this on a clean build, same problem
#3
05/02/2004 (7:52 am)
It seems like Davis met with this problem, too. I'm not sure.
#4
05/02/2004 (10:09 am)
You can even watch the object move by checking the position field in the editor. So if you press F10 repeadatly, you'll get a nice mosaic! ;D
#5
05/02/2004 (1:07 pm)
Lame. Have you tried fixing the relative positioning formula for it? Sounds like something is off a tiny bit.
#6
I saw a resource about Relative being broken in a old version though, will check it out as soon as I get time.
Edit: Grammar.
05/02/2004 (4:00 pm)
Math is not my strongest ability ;) Even so, I don't know where to look, (guess it could be in array, control or types) and I'm full with other stuff to look at :/I saw a resource about Relative being broken in a old version though, will check it out as soon as I get time.
Edit: Grammar.
#7
I'd hazard a guess that someone didnt cast some int's to floats before doing a multiply.
If you look in guicontrol.h + .cc you'll find all the code you'd need to fix it.
05/02/2004 (4:31 pm)
If its only a few pixels, its probably some integer math coordinate problem. Basically the gui controls are set in integer coordinates. Which means any floating point math is going to have some errors introduced when you do stuff like relative scaling.I'd hazard a guess that someone didnt cast some int's to floats before doing a multiply.
If you look in guicontrol.h + .cc you'll find all the code you'd need to fix it.
#8
04/08/2009 (8:45 am)
The problem on bitmap in playgui still exist. I've got objects that continuosly moves toggling F10.
#9
04/08/2009 (8:46 am)
I think is a problem with combinations of "...Sizing values". The really strange things is that the numerical values of position change! And are saved also!
#10
04/08/2009 (8:58 am)
I discover the funny stuff....right is left, bottom is top...anchor seems to work in the opposite direction....but I think that is half of the bug...
#11
04/09/2009 (1:18 am)
Half side: if the item ( on UI is left, top hooked ) is selected when you toggle with F10 it behaves like is centered, so toggling continuosly beetween the two behaviour ( left,top (for UI ) and center,center ) makes the object moving.
#12
One would think it would get fixed by GG *sometime* over the last 5 years.. lol
Anyone got a fix, or know where to look to fix this?
04/09/2009 (5:38 am)
I've had this exact same problem when using relative..One would think it would get fixed by GG *sometime* over the last 5 years.. lol
Anyone got a fix, or know where to look to fix this?
Associate Kyle Carter