Vector gauges programming question

[Guest]

Integers and floats and mixing them are not trivial issues. I had a problem where I couldn't overlap a temporary and a selected heading bug when they should have been the same value. Turns out one was measuring an integer value and the other a float. Took me a while to find that one.Bill

[mfrantz 45]

Hi Bill,Thanks for your interest. It is not a problem of code. I get this behaviour even when compiling and testing the SDK FlightMap example as it is - with no changes at all in the original code.So I guess the problem is somewhere else - system (WinXP), compiler (Bcc55), hardware or whatever :-hmmm Michael>Michael,>>Post the code snippet that's giving you the problem.>>Bill

[Guest Fabio Miguez]

Hey Michael. Just checking back to see if you were able to solve this weird problem you were having? I hope so.By the way, I wish to congratulate you on such a great utility that ServInfo is. I cannot fly without it anymore, and it is extremelly well done. I am sure I speak for the entire crew here, great friggin job!

[Guest ba747heavy]

>I am sure I speak for the entire crew here, great friggin job!Here here!

[mfrantz 45]

Thanks a lot Fabio and Fred.No, I have not solved this yet, I am just used to it now :-) Michael

[Guest Fabio Miguez]

Hey Michael.Where are you declaring PIXPOINT? I would suggest you try the following:Declare PIXPOINT dim; somewhere early in the code, before any macros, after the header.In PANEL_SERVICE_PRE_DRAW, declare:pelement = (PELEMENT_STATIC_IMAGE)(pgauge->elements_list[0]->next_element[0]);dim = pelement->image_data.final->dim;Sometimes FS doesn't like when you declare things on the fly and use them in the same line, as in dim. Let us know if anything changes.P.S. Don't forget, because of HTML tags, a < means [