rodrigofarias77
31-07-2007 22:12:40
KungFooMasta, currently QuickGUI has 3 metrics modes. Do you plan to add another pixel mode, related to the parent widget? The available pixel mode is related to the screen, right?
The current version of CEGUI uses the unified dimension. Do you plan to implement something similar?
Regards
Rodrigo
kungfoomasta
31-07-2007 23:09:19
I don't plan to add another, I don't see anything missing from the 3 I have provided. If you have pixel relative to parent pixel, that is a percentage, which is identical to relative dimensions.
Maybe you can explain more about unified dimension. Or, more importantly, what is lacking that you need?
rodrigofarias77
01-08-2007 18:16:58
CEGUI uses the sintax window->setPosition(UDim, UDim), for example, to position a widget. The syntax of the Unified Dimension is UDim(scale, offset). The scale is relative to the parent window, in the range [0,1]. The offset is measured in pixels.
Regarding to the metrics modes features of QuickGUI, do not worry, nothing is lacking. We just need to change a little our code to achieve the same results.
Regards
Rodrigo
thecaptain
01-08-2007 21:15:50
Actually, I was thinking of something similar, because then it allows better scaling of HUDs or something for strange screen resolutions. However, I don't know if this needs to be implemented in 0.9.6. I'd probably suggest putting it in 0.9.7 or something, after we figure out the exact advantages and best way to use it.
rodrigofarias77
06-08-2007 23:20:44
KungFooMasta, I have discovered that even when we use the mode
QGUI_GMM_PIXELS, the metrics are not relative to the screen, but to the parent widget. To be honest, I prefer this way
Regards
Rodrigo
kungfoomasta
07-08-2007 01:18:57
With v0.9.5 everything was boiled down to pixel coordinates, to use with Overlays. With v0.9.6, the underlying values used for rendering will be absolute coordinates. Even so, there may be some bugs in my code to calculate/convert between relative/absolute/pixel.
If you have any problems let me know! (I will look into problems after v0.9.6)