BRT Community

Please login or register.

Login with username, password and session length
Advanced search  


Welcome to the Bridgetek Community!

Please read our Welcome Note

Technical Support enquires
please contact the team
@ Bridgetek Support

Please refer to our website for detailed information on all our products - Bridgetek - Bridging Technology

Author Topic: Line vs text or number  (Read 286 times)


  • Newbie
  • *
  • Posts: 20
    • View Profile
Line vs text or number
« on: January 20, 2022, 12:45:36 AM »


just to be sure to be on the right track...

I can "create/move" lines/rects/points/etc. with a precision of 1/16 pixel with VERTEX2F. But this is not possible with CMD_TEXT, CMD_NUMBER, VERTEXII and a font. There is the precision of 1 pixel...?
Or is there a way to do text/numbers with the same precision, or i am completely wrong here?

Thank you for your help


BRT Community

  • Administrator
  • Hero Member
  • *****
  • Posts: 561
    • View Profile
Re: Line vs text or number
« Reply #1 on: January 21, 2022, 12:06:26 PM »


Most of these items are positioned by the pixel rather than by 1/16th. When used in code examples, you will see that Vertex2F has the value multiplied by 16 e.g. VERTEX2F(20*16, 20*16) to place something at coordinate 20,20. Note that you can actually also display numbers and letters using VERTEX2F as they are made up of a series of images (one per character).

Also note that using the text command does all the character spacing etc for you. If you use Vertex2F this only places 1 character per vertex and so to make a string of characters you will need to call a Vertex2f per character.

It is possible to just add a value to the x coordinate each time but if you want the text to look proportional (and so spacing between each char related to the width of the char) then you can use the metric block data/font properties which is in the EVE chip. For numbers you might want a fixed position for each number so that the whole number does not move around and change in length (e.g. a 1 is narrower than an 8 ) but for text, having a constant spacing between characters may not look as good.

Best regards

BRT Community