TBilt -- pixels vs user-defined coordinates

Is there any documentation that discusses the pros and cons of defining True Controls by pixels (required by TBilt) vs user-defined coordinates (the default in True Basic itself)? I've written statistical software using TrueBasic and placed it in the public domain. Users have screen resolutions unknown to me. I presume that pixel-defined controls will generate errors if user resolution is too low -- is this right? For example, will the TBilt-generated code CALL TC_Win_Create (winid_1, "TITLE|CLOSE", 77, 886, 600, 125) run if screen resolution is only 800 x 600? Do I need to adapt TBilt code by replacing pixels with user-defined coordinates that are independent of screen resolution?

Thanks for your counsel and guidance...

Bill Roberts


adapting to different screen resolutions

Thanks for your feedback and the tip. I'll give it a try.

Best regards,



Hi Bill,

There is a brief description of the pros and cons of pixel versus user units in the manual for the BronzeTC library. Basically it is easier to locate printed text and images with pixel units, and of course the units are always whole numbers. User units have the advantage that you don't have to worry about screen size but the units are always decimals - usually to at least 3 places. The problems arise when you design a complex screen full of buttons, edit boxes etc to suit say 1024x786 and you move it a screen 640x40 then the objects will be resized correctly but the text won't. Likewize scaling up will give you huge push buttons with a very small legend.

Personally I always use pixel units. To get around the screen size you can use:
ASK PIXELS xpix,ypix
SET WINDOW 0,xpix-1,ypix-1,0

If you then dimension all your objects relative to the center of the screen you won't have any trouble.

Big John