VC tooltips

[DragonflightDesign]

I really have no idea where to put this thread, so here seems as good a place as any.

I've been told by one modeller that it isn't possible to add dynamic tooltips to a VC clickspot, but I'm also being told by a user that he has seen them. So if this is the modeldef code for the rudder trim (yes Roman - you have seen this before! )

<PartInfo>
        <Name>RudderWheel</Name>
        <AnimLength>360</AnimLength>
        <Animation>
            <Parameter>
                <Code>
                     (L:RudderWheel, number) 225 + 45 % 8 * 0 max 360 min
                </Code>
            </Parameter>
        </Animation>
        <MouseRect>
          <Cursor>Hand</Cursor>
            <MouseFlags>LeftSingle+LeftDrag</MouseFlags>
            <CallbackCode>
                            -20 20 (L:RudderTrimPos, number) rng (M:Event) 'LeftSingle' scmp 0 == and
                            if{
                                (M:X) (&gt;L:MouseX32, number)
                                (M:Y) (&gt;L:MouseY32, number)
                                (L:RudderWheel, number) 0.1111111 * -20 max 20 min (&gt;L:RudderTrimPos, number)
                            }

                            -20 20 (L:RudderTrimPos, number) rng (M:Event) 'LeftDrag' scmp 0 == and
                            if{
                                (L:RudderWheel, number) (M:X) (L:MouseX32, number) - 0.05 * + -180 max 180 min (&gt;L:RudderWheel, number) (M:X) (&gt;L:MouseX32, number)
                                (L:RudderWheel, number) (M:Y) (L:MouseY32, number) - 0.05 * + -180 max 180 min (&gt;L:RudderWheel, number) (M:Y) (&gt;L:MouseY32, number)
                                (L:RudderWheel, number) 0.1111111 * -20 max 20 min (&gt;L:RudderTrimPos, number)
                            }
             </CallbackCode>
         <TooltipText>Rudder Trim Wheel</TooltipText>
        </MouseRect>
    </PartInfo>

- how do I add L:RudderTrimPos to the tooltip? And no, I have almost no idea what I'm doing when it comes to programming the modeldef.

 

[spokes2112]

Very, very familiar! heh
You could try -

<TooltipText>Rudder Trim (%((L:RudderWheel, number) s0)%{if}%(l0 0.555555556 * abs)%!d!%% %(l0 0 &gt;)%{if}right%{else}left%{end}%{else}straight%{end})</TooltipText>

Depending on the rest of code ( IE how the trim wheel is implemented into the trim tab ), you may have to swap the "left" & "right"
If it works, the same code could be used for aileron & elevator by changing the L:Var, the beginning text and again either : swapping "left" for "right" & swapping "left" / "right" for "up" / "down".
This is because it is based on the raw +/- 180 limits, which is the same in all 3 versions, not the calculated position of the indicator.

 

[DragonflightDesign]

Aaaaaaaaaha! Gotcha Roman!

 

[OzWookiee]

Very, very familiar! heh
You could try -

<TooltipText>Rudder Trim (%((L:RudderWheel, number) s0)%{if}%(l0 0.555555556 * abs)%!d!%% %(l0 0 &gt;)%{if}right%{else}left%{end}%{else}straight%{end})</TooltipText>

Depending on the rest of code ( IE how the trim wheel is implemented into the trim tab ), you may have to swap the "left" & "right"
If it works, the same code could be used for aileron & elevator by changing the L:Var, the beginning text and again either : swapping "left" for "right" & swapping "left" / "right" for "up" / "down".
This is because it is based on the raw +/- 180 limits, which is the same in all 3 versions, not the calculated position of the indicator.

Yuyp that would be it

 

[DragonflightDesign]

Well, almost gotcha! I can't figure out where

(l0 0.555555556)

is derived from?

 

[WarpD]

Dai... L:RudderWheel, number was put into s0... and l0 was used to extract it... and then that value was multiplied by 0.55555556 and the resulting value was resolved to a positive value and then... well, it goes on and on... LOL I don't know what the 0.55555556 represents... but the l0 is just a way to use what was stored by s0.

 

[spokes2112]

(L:RudderWheel, number) is stored in register in s0 and checked right away by an {if}. Zero, (false) is the only value that will bypass this {if} because there is no comparison to check, if so, it then goes all the way to the end %{else}straight%{end}
If not a zero, this first {if} is true, then -
Register s0 is retrieved ( l0 ), it has a range of -180 to 180 where we need a absolute ( "abs" - positive number only) as a percentage. 180 * 0.55555556 = 100.00000008, close enough, it is rounded in the print code %!d!%.
The full code of the percentage display - %(l0 0.555555556 * abs)%!d!%% %
Now we figure out if it's left or right.
Register s0 is retrieved again ( l0 ), it has a range of -180 to 180, we already know it can't be a zero, that was handled earlier, but we can check to see if it's greater or less than zero.
(l0 0 >) - if it's greater than, then it's right trim, otherwise it's left. %{if}right%{else}left%{end}%

 

[DragonflightDesign]

@Ed: that clears up one thing. I thought IO was ten

@ Roman: I think I follow that - the output is in percentage, not in degrees. So for the aileron trim where the full movement is 12.5 degreees either side of zero:-

%(l0 0.125 * abs)%!d!%% %

Yes? No?

 

[spokes2112]

No..
The value is taken from (L:RudderWheel, number). What you do with that value afterwards to command the +/- 12.5° trim will end up the same.
The L:var equals 180, you are commanding 12.5° both are at 100%
The L:var equals -180, you are commanding -12.5° both are at 100% ( of course with "abs" )

 

[gaabne]

May I add that the Learning Center list a lot of TooltipID which can be used asis,
But also show the corresponding TooltipText from which you can easily derive most of what one needs,
the syntax being a real nightmare..

My two cents... and Mery Chrismas

Gérard