Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
NT8 Get String Size (Used to be Graphics.MeasureString in NT7)
I have been slaving over conversions from NT7 to NT8 lately and I ran into an issue that I just can't find the solution to.
Let's just get to the point. I am trying to build an arrow with text that doesn't overlap when you change the chart scale or zoom in and out (this I have figured out), but the issue now is when I try to have 2 arrows with text one above the other, and scale the chart of course. What I feel is missing is the ability to use a Grapics.MeasureString so I can get the size in pixels of the text and plot the arrow below or above what ever the case might be.
Does anyone have any idea how to "Measure String" in NT8 or something similar?
Thanks in advance,
Maza.
Can you help answer these questions from other members on NexusFi?
Ok so I solved the issue, kind of, and I will write it here if anyone else wants to do this sort of thing in the future.
First of all I got the price from arrow1 and I changed it to pixels, then I added a few pixels and the custom auto pixeling bit of code that accounts for the scaling of the arrows and, to my surprise that it worked, I added the size of the font to the arrow1 pixels, then transformed it all back to price and set arrow2 price to the newly calculated price.
I hope this helps anyone that comes across the same problem in the future.
