• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Dual function switch for MFD

Messages
542
Country
australia
I have a page in a MFD in which the top half of the display has 2 different displays toggled by a visability condition , the toggle switch works.
Each of the 2 displays has it's own switches , I am having difficulty getting those switches to work.

This is the current switch code:
HTML:
	<Macro Name="Button1">(L:DAT49 mode,enum) 3 == if{ (K:VOR1_OBI_INC) } (L:DAT49 mode,enum) 4 == if{ 4 (>L:Tritium, enum) }</Macro>
    <Area Left="4" Top="5" Width="20" Height="20">
      <Cursor Type="Hand"/>
      <Click Kind="LeftSingle" Repeat="Yes">(L:DAT49 mode,enum) 3 == if{ (>K:VOR1_OBI_INC) } @Button1</Click>
    </Area>

The MFD page is selected by:
HTML:
(L:DAT49 mode,enum) 4 ==

The area of concern is:
HTML:
if{ 4 (>L:Tritium, enum) }

What is required is something along the following lines for the "if" condition:

(A) if L:Display mode, enum is 0 (the visible call)
then 4 >L:Tritium,enum (the first action req'd)

(B) els L:Display mode, enum is 1 (the visible call)
then 6 >L:Cobalt,enum (the second action req'd)

Any ideas of the correct format ?

Cheers
Karol
 
<Click Kind="LeftSingle" Repeat="Yes">(L:DAT49 mode,enum) 3 == if{ (>K:VOR1_OBI_INC) } @Button1</Click>

The red part is duplicated, it's already included in the macro.

Honestly I find your intentions rather confusing. Could you state just in plain words what does each switch need to do?

Tom
 
Tom

This shot shows the MFD .
TyEQ3.jpg
fsx 2013-03-25 23-17-29-80.jpg


The portion of code you refer to is in another page of the MFD and works OK.

My problem is in this part of the code.
HTML:
(L:DAT49 mode,enum) 4 == if{ 4 (>L:Tritium, enum) }
" (L:DAT49 mode,enum) 4 " opens the fifth page boxed in blue in the shot.
The " if " portion is the old switch function portion.

As can be seen in the shot I have added a toggle to display 2 different views,
this toggle is the usual visability selection , either:
L:Display mode, enum 0 or L:Display mode, enum 1

What I now need is a " if " " els " conditional statement to replace
HTML:
if{ 4 (>L:Tritium, enum) }

This statement needs to account for the the " Visability " as follows:
(A) if L:Display mode, enum is 0 (the visible call)
then 4 >L:Tritium,enum (the first action req'd)

(B) els L:Display mode, enum is 1 (the visible call)
then 6 >L:Cobalt,enum (the second action req'd)

Cheers
Karol

PS: Following composite shot shows instrument where
Lat/Long positions have been added to a flight plan.
SEQ 4 -Arnsberg Germany (degrees and decimals)
SEQ 5 -Morton Derbyshire UK (D:M:S)
SEQ 6 -Chesterfield Derbyshire UK (degrees:minutes and decimals)
SEQ 7 -A point near the aircraft at YAMB nominated by Radar screen Pick up.
fsx 2013-03-25 22-26-47-63.jpg

The aircraft was parked at YAMB during the Wpt entries.
One of the Radar screens is a Stand off view of SEQ 4.
QIr9.jpg
 
Last edited:
Further explanation.
I created 2 development instruments :
1. ICAO Wpt Entry.
2. Lat/Long Wpt Entry with 3 Lat/Long formats.

I am now trying to shoehorn their functions into my MFD.

The composite shot was created using both the MFD and one of the Development instruments as the top 3 left and 4 right MFD buttons are not yet functional (t he reason for this thread)

Cheers
Karol
 
Last edited:
So, when you press PLN button, you need the current SEL (LAT/LON or ICAO) to display, and obviously need to know which SEL is active, am I correct?

Tom
 
Tom

Sorry that my description is not Clearer.

Following is the button protocol.

The bottom row of buttons select MFD pages
ie;
Fuel , Engine , Radio , ADI , PLN-flight plan editor.

The left and right button columns only control aspect within the individual chosen page.
******
Specific to this thread :-

1. The " PLN " button opens the flight plan editor , the default view is the ICAO entry one.

then

2. The " SEL " button then toggles either ICAO view or LAT/LONG view.
This is a ' visability ' condition :-
ICAO = L:Display mode, enum is 0
LAT/LONG = L:Display mode, enum is 1

then

3. Vertical column buttons :-

LEFT SIDE.
these open the keyboard and allow a entry to be typed.

ICAO --------------------------- LAT/LONG
DTO - L:FPEntry, enum (n) ---- LL1 - L:FPEntry, enum (n)
S.1 - L:FPEntry, enum (n) ---- LL2 - L:FPEntry, enum (n)
S.2 - L:FPEntry, enum (n) ---- LL3 - L:FPEntry, enum (n)

RIGHT SIDE.
these actually enter the then displayed ICAO or LAT/LONG into a
flight plan utilising if necessary the " Index " number that has been set
in the thumbwheel.

All buttons are labelled " ENT " , but the script is individually dependant on what is being entered.
Following is one example :
HTML:
(L:latitude test,number) (>@c:FlightPlanNewWaypointLatitude, degrees)
                (L:longitude test,number) (>@c:FlightPlanNewWaypointLongitude, degrees)
				'TGT' (L:F111_Wpt_Sum, number) near scat (>@c:FlightPlanNewWaypointIdent)			
				(L:F111_Wpt_Sum, number) (>@c:FlightPlanAddWaypoint)
				0 (>L:FPEntry, enum)
				0 (&gt;C:fs9gps:IcaoSearchStopCursor)

Cheers
Karol
 
I'm still not sure to be following you but, as an example, you can code something like (verbose)

Code:
Button DTO Area
<Click>
    (LAT49 mode,enum) 4 == (L:DisplayMode,enum) 0 == and
    if{ Display Keyboard and allow ICAO entry for DTO }
    (LAT49 mode,enum) 4 == (L:DisplayMode,enum) 1 == and
    if{ Display Keyboard and allow LATLON entry for DTO }
</Click>
Button S1 Area
<Click> the same logic as above, for S1
Button (DTO) ENT on right side
<Click>
    (LAT49 mode,enum) 4 == (L:DisplayMode,enum) 0 == and
    if{ Enter DTO ICAO entry into FP }
    (LAT49 mode,enum) 4 == (L:DisplayMode,enum) 1 == and
    if{ Enter DTO LATLON entry into FP }
</Click>
As you can see, looks too much simple so I guess I'm not getting your point very well...

Tom
 
Bob

Thank you , it's cool fun putting some of these useful capabilities into a panel.
When I have the messy button situation sorted and working , I will be posting the full working 'keyboard Lat/Long Wpt entry" instrument
code for the communities use as they see fit .
There are some very useful and unique instruments that can flow from the Lat/Long entry.

Tom

The MFD Mouse area is a bit of a complex Maze , and what I'm trying to add to it only makes it worse .
I apologise for not providing a more concise description that better shows the
flow chart style of function.
Thank you for you ideas , I will try to see where they lead.

I had a little progress ( I think ) very late last night for the top left-right buttons , they control :

either ... DTO .. or toggle .. Lat/Long ( in D:M:S format )

I will run a few more tests with them , and then post the full code for
those 2 buttons.
That might clarify what I'm trying to do.

Thank you for your patience , it's greatly appreciated.

Cheers
Karol
 
Last edited:
I have to admit to being confused.
I really don't know what I'm doing !?? !!

However the following works ! !

HTML:
    <!--==== LEFT BUTTONS ====-->
<!-- Either  DTO  or  LL1  button -->	
	<Macro Name="Button1">(L:DAT49 mode,enum) 3 == if{ (K:VOR1_OBI_INC) } (L:DAT49 mode,enum) 4 == if{ (L:Display mode,enum) 0 == }
           	if{ 4 (>L:FPEntry, enum) }
			els{ (L:Display mode,enum) 1 == }
			if{ 5 (>L:FPEntry, enum) }</Macro>
    <Area Left="4" Top="5" Width="20" Height="20">
      <Cursor Type="Hand"/>
      <Click Kind="LeftSingle" Repeat="Yes">(L:DAT49 mode,enum) 3 == if{ (>K:VOR1_OBI_INC) } @Button1</Click>
    </Area>

HTML:
    <!--==== RIGHT BUTTONS ====-->
<!-- Either  ENT  or  ENT button     Different functions but same button name -->		
    <Macro Name="Button7">(L:DAT49 mode,enum) 2 == if{ (>K:COM_RADIO) (>K:FREQUENCY_SWAP) } (L:DAT49 mode,enum) 4 == if{ (L:Display mode,enum) 0 == } if{ 'A' (>@c:IcaoSearchStartCursor)
				(L:F111-DTO-4,number) chr (L:F111-DTO-3,number) chr 
				(L:F111-DTO-2,number) chr (L:F111-DTO-1,number) chr scat scat scat (>@c:IcaoSearchEnterChar) 
				0 (>@c:FlightPlanWaypointIndex)
				(@c:IcaoSearchMatchedIcaosNumber,number) 0 &gt; 
					if{ (@c:IcaoSearchCurrentICAO) (>@c:FlightPlanNewWaypointICAO) } 
				1 (>@c:FlightPlanDirectToDestination)
                0 (>L:FPEntry, enum)
				0 (>L:F111-DTO-1,enum) 0 (>L:F111-DTO-2,enum) 0 (>L:F111-DTO-3,enum) 0 (>L:F111-DTO-4,enum)	}
				 els{ (L:Display mode,enum) 1 == }
			    if{ (L:latitude test,number) (>@c:FlightPlanNewWaypointLatitude, degrees)
                (L:longitude test,number) (>@c:FlightPlanNewWaypointLongitude, degrees)
				'TGT' (L:F111_Wpt_Sum, number) near scat (>@c:FlightPlanNewWaypointIdent)			
				(L:F111_Wpt_Sum, number) (>@c:FlightPlanAddWaypoint)
				0 (>L:FPEntry, enum)
				0 (&gt;C:fs9gps:IcaoSearchStopCursor) }</Macro>
    <Area Left="197" Top="5" Width="20" Height="20">
      <Cursor Type="Hand"/>
      <Click Kind="LeftSingle">(L:DAT49 mode,enum) 3 == if{ 0 (>K:TOGGLE_GPS_DRIVES_NAV1) } @Button7</Click>
    </Area>

PROCEDURE:
1. Hit " PLN " button of the MFD.
Flight Plan Editor then displays (1) ICAO page view (see initial screenshot)

2. Hit " DTO " button , then a blue box appears on screen.

3. On your computer Keyboard , type in your preferred ICAO ie; EGCC
That ICAO appears in the blue box.

4. Hit the " ENT " button that is on the same horizontal level.
Your DTO is now entered as a flight plan that can be flown.

ALTERNATELY.
Putting in a Lat/Long Wpt in D:M:S format , into an existing Flt Pln.
1. Hit " SEL " button , screen view will change from (1) ICAO page view
to (2) LAT/LONG page view.

2. At the Thumbwheel set the SEQ/INDEX number that will dictate where the
Wpt is to be inserted in the Flt Pln.

3. Hit " LL1 " button , blue box appears.

4. On Keyboard type in the Latitude and Longitude.

5. Hit the " ENT " button , your Wpt has now been added to the flight plan
at the SEQ number that you nominated.
*********

It still requires addition of other buttons and some thorough testing.

Cheers
Karol
 
That seemed to be the required format in the Mouse section.
All button functions now installed .
The MFD - Flight Plan Editor is now fully functional , and it works as desired.
Preliminary testing indicates that all the buttons are working in both of the views.

It's definitely a fun instrument to use.
With the 3 Lat/Long formats all options are covered , you can read off a map or google the Lat/Long of Machu Picchu which appears in a Decimal format as do the automobile GPS or camera Geo function.
The Degree: Minute and decimal was included as it is used in military instruments.

Off to do more testing.

Cheers
Karol
 
Karol, your project looks very interesting. It seems you applied part of the logic I posted and it worked :) Good jobl!

Tom
 
There are some very useful and unique instruments that can flow from the Lat/Long entry.

Yeah, I agree with you - the most fun I have is playing around with gps / MFD instrumentation.

Next, I am waiting for you to add mouse click (or touch screen) waypoint addition - retiring keyboard entry completely, if you want :)

With your add waypoint section, it looks like entry is for, in my terminology, the "Ident" rather than ICAO. Safe for airports, but if VOR, for example, are you checking for and resolving multiple Idents?

Bob
 
Last edited:
Tom

Thank you for that sample , my immediate impression was to use it in an experimental " switching " instrument , as you know MFDs , FMS and CDU's rapidly become switch nightmares.
For my own curiosity I want to create a large scale MFD with a tree like structure ( branching ).
The main problem apart from the switch protocols would be keeping it intuitive and pilot friendly , so that it remains both simple and fast to use.

That is the latest version of a freeware panel that I concentrate on , Titled ' F-111 Pig HUD ' Situational awareness cockpit , it's kind of a concept panel along the lines of how a analogue panel might be progressively be modernised and upgraded to digital , I do it for my own personal style of flying , but it's OK so
I share it as freeware , it does have some interesting instrument in it.
Problem is I have to rewrite the Flight Manual to enable an upload of this latest version , and typing is NOT my favorite pastime .


Again , thank you for your help.

Bob

I found that as I added features and capabilities to my Radar that it was trending towards a MFD , but it's not a MFD , then I realised that purely by accident it was evolving toward a " Battle space " instrument.
I'm sure that you have seen the cool one in the JSF F-35.
As always the problem is to shoehorn a massive amount of data/information and graphic displays into the limited real estate available in a panel and at the same time keep it all simple and fast to use as well as pilot friendly.

For simplicity sake the Mission adaptive Flight plan editor was restricted to
(A) Airport ICAOs and (B) LAT/LONG entries only.
Note that the forth Lat/Long entry is sourced from moused touch screen point
nominated in the radar unit ( as per your Custom Draw Hand book ) ,
it's the little red dot 16.11 Nm from the aircraft in the above screenshot.

While I agree that Touch Screen is fantastically important , I also feel that
the keyboard style option of data entry remains as an adjunct for pilot use.
At the following link note the Airbus pilot's use of the humble keyboard.
http://www.wimp.com/approachlanding/

Cheers
Karol
 
Last edited:
KEYBOARD DATA ENTRY
ON KEYS
LATITUDE / LONGITUDE WAYPOINT ENTRY


A while back I conducted searches to gather information on the subject of
using the Keyboard to enter typed data and on the use and structure of
On Keys .
I was surprised that searches came up empty.

I have now created 2 separate instruments that use the keyboard to enter
(A) Airport ICAO waypoints , a link was provided above that provided the full instrument.
and
(B) Lat/Long waypoints , The full instrument code is provided at the end of this post.
These both can be copied and used as working instruments or used as information examples.

The following provides further material on the topic.

REFERENCES
(A) GPS Guide book - FS9GPS MODULE V1.1 By Bob McElrath .
specifically 'Keyboard direct entry' pages 184 to 187 .
An important read on the subject.
(B) Post # 25 of the following link generally details the structure used in the Lat/Long instrument
http://forum.avsim.net/topic/373377-q-add-waypoint-to-flightplan-or-nav12-using-latlon-input/
********
The Lat/Long Wpt entry instrument.
- Attached zip has instrument folder and procedure notes
- Make an entry in it's panel cfg along the following lines
gaugeXX=Xplan!Dusty, 1,1,228,205

Then fly and use it .

Cheers
Karol
View attachment Xplan,zip.zip

PS: if you install both instrument you get full coverage of Wpt entries similar to those in above screenshots.
 
Last edited:
I have extracted the Duel editor out of the MFD.
The attached instrument has both ICAO and Lat/Long rolled into one instrument ,it has the SEL button to toggle displays.

Basically this unit is exactly as per original screenshots , much more pleasing.

Suggested panel cfg entry is
gaugeXX=Xplan!Dinky, 1,1,228,205

NOTE . if you get double character display entries it indicates that you have 2 versions of editors loaded.

Note also that the RDR PU (radar pick up will not work as it is fed by a appropriatley modified radar which is not included in the zip)

Cheers
Karol
 

Attachments

I have made a few additional changes to the Flight plan editor.
This is what it looks like now.
Fz9Ho.jpg
fsx 2013-04-15 16-39-40-54.jpg


This shot basically shows the functions.
wzPUB.jpg
fsx 2013-04-13 23-26-39-79.jpg


If you look at " BLOCK 2 " in the shot , the description states " Add Waypoints " , and that was exactly what it did for each of the 5 lines.

Add Waypoints is kind of restrictive from a in flight view point.
For example if you wanted to replace your current flight plan SEQ/INDEX #6 with a Lat/Long , then it would entail adding it as SEQ #6 , then deleting SEQ #7 which had previously been at #6 before it was incremented.
I wanted a direct swap by a single action.

Additionally , I thought it would be nice to be able to insert a Lat/Long as a DTO in a single action.

Basically what I was after a method to ENTER any of the 5 lines in Block 2 as either , Add Waypoint , or DTO (Direct To) , or Replacement.

I created a "TYP" button that toggles ADD - DTO - REP.
HTML:
(L:TypEntry, enum) ++ 3 % (&gt;L:TypEntry, enum)

With readout.
HTML:
<Element>
              <Position X="177" Y="114"/>
              <FormattedText X="30" Y="10" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="LEFT" Color="#CC9900" Bright="Yes">
                <String>%((L:TypEntry))%{case}%{:0} ADD%{:1} DTO%{:2} REP%{end}%</String>
              </FormattedText>
            </Element>

Then in "ENT" button switch I utilised the code exactly as provided by Tom at a post #8 above.
The following is entry code for the Lat/Long Degrees to 4 decimal places.
HTML:
      <Macro Name="Button9">(L:DAT49 mode,enum) 2 == if{ (>K:NAV1_RADIO_SWAP) } (L:DAT49 mode,enum) 4 ==
            (L:Display mode,enum) 1 == (L:TypEntry, enum) 0 == and and
              if{ (L:latitude best,number) (>@c:FlightPlanNewWaypointLatitude, degrees)
                (L:longitude best,number) (>@c:FlightPlanNewWaypointLongitude, degrees)
                'TGT' (L:F111_Wpt_Sum, number) near scat (>@c:FlightPlanNewWaypointIdent)          
                (L:F111_Wpt_Sum, number) (>@c:FlightPlanAddWaypoint)
                0 (>L:FPEntry, enum)
                0 (&gt;C:fs9gps:IcaoSearchStopCursor) }
            (L:DAT49 mode,enum) 4 == (L:Display mode,enum) 1 == (L:TypEntry, enum) 1 == and and
              if{ 0 (>@c:FlightPlanWaypointIndex)
                (L:latitude best,number) (>@c:FlightPlanNewWaypointLatitude, degrees)
                (L:longitude best,number) (>@c:FlightPlanNewWaypointLongitude, degrees)
                'TGT' (L:F111_Wpt_Sum, number) near scat (>@c:FlightPlanNewWaypointIdent)
                1 (>@c:FlightPlanDirectToDestination)
                0 (>L:FPEntry, enum) }
         (L:DAT49 mode,enum) 4 == (L:Display mode,enum) 1 == (L:TypEntry, enum) 2 == and and
              if{ (L:latitude best,number) (>@c:FlightPlanNewWaypointLatitude, degrees)
                (L:longitude best,number) (>@c:FlightPlanNewWaypointLongitude, degrees)
                'TGT' (L:F111_Wpt_Sum, number) near scat (>@c:FlightPlanNewWaypointIdent)          
                (L:F111_Wpt_Sum, number) (>@c:FlightPlanAddWaypoint)
                (L:F111_Wpt_Sum, number) 1 + (>@c:FlightPlanDeleteWaypoint)              
                0 (>L:FPEntry, enum)
                0 (&gt;C:fs9gps:IcaoSearchStopCursor) }</Macro>
    <Area Left="197" Top="64" Width="20" Height="20">
      <Cursor Type="Hand"/>
      <Click Kind="LeftSingle" Repeat="Yes">(L:DAT49 mode,enum) 3 == if{ (>K:HEADING_BUG_INC) } @Button9</Click>
    </Area>

It works a treat .
(1). At "TYP" button set entry mode required ADD-DTO-REP.
(2). Then hit any of the 5 line "ENT" buttons.

It's fantastic , it radically changes the Editor instrument.

BUT ... Unfortunately as is often the case , I have run out of buttons.
I had to place the "TYP" button on the ICAO page , when it's primary duties are on the Lat/Long page , it's an absolute pain , not satisfactory.

I now want to transfer it to a on screen hot spot on the Lat/Long page.

My problem is that I want the following "TYP" mode text readout to appear.
ADD ... DTO ... REP in one colour , with the current selected mode to be in a different colour as shown.

How do I write that code ?

Any advice greatly appreciated.

Cheers
Karol
PS: the following code will at a single click 'Scrub' a flight plan completely , regardless of how long that flight plan is.
HTML:
0 (>@c:FlightPlanDirectToDestination)
                1 (@c:FlightPlanWaypointIndex) (>@c:FlightPlanDeleteWaypoint)
                0 (@c:FlightPlanWaypointIndex) (>@c:FlightPlanDeleteWaypoint)
 
Last edited:
Hi,

Here is a fragment of a formatted text element:

Code:
<FormattedText X="228" Y="500" Font="@FONT_TRG" Adjust="left" FontSize="14"
Tabs="0" LineSpacing="18" Color="#222222" Bright="Yes">
<Font FontSize="20"/>
<Font FontSize="15"/>
<Font FontSize="10"/>
<Color Value="#FF0000"/>
<Color Value="red"/>
<Color Value="#ff00ff"/>
<String>
%((G:Var8) 0 == )%{if}<!-- Page 1 -->
Takeoff: Flaps 2, 4° Trim UP,\n
%((L:WATER_1,bool) 1 == ) %{if}Full Throttle\n%{end}
%((A:Sim on Ground, bool) (L:WATER_1,bool) 0 == &amp;&amp; )%{if}\{clr2}No ADI  53" MAP 2700 RPM\{clr1}\n%{end}

The last line changes the text and the color if the test code is true. You can see how I am changing the color to red - {clr2}, <Color Value="#FF0000"/>, then changing it back again to the default color {clr1}

You can do this anywhere in your code, whether conditional or not.

Hope this helps,
 
Finally finished it.

I tried to adapt the above code , but found it to be rather difficult , so I cheated and did it the easy way.
Over the top of the white ADD ... DTO ... REP , I placed applicable orange active text with a green background at the appropriate location.
It is not elegant coding wise but it works nicely.
Code is.
HTML:
 <!-- ENTRY MODE  -->   
        <Element>
          <Position X="33" Y="6"/>
          <FormattedText X="97" Y="9" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="LEFT" Color="#349F34" Bright="Yes">
            <String>%SET ENTRY MODE >>%</String>
          </FormattedText>
        </Element>   

<!-- MODE list - - ADD - DTO - REPLACE -->   
            <Element>
              <Position X="120" Y="6"/>
              <FormattedText X="70" Y="9" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="LEFT" Color="#A1A9A6" Bright="Yes">
                <String>%\tADD    DTO    REP%</String>
              </FormattedText>
            </Element>
<!-- ENTRY MODE  -->
    <Element>
      <Visible>(L:TypEntry) 0 ==</Visible>   
        <Element>
          <Position X="120" Y="6"/>
          <FormattedText X="25" Y="9" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="CENTER" Color="#ED7300" BackgroundColor="#164516" Bright="Yes">
                <Color Value="#A1A9A6"/>     
            <String>%ADD%</String>
          </FormattedText>
        </Element>
    </Element>
    <Element>
      <Visible>(L:TypEntry) 1 ==</Visible>   
        <Element>
          <Position X="145" Y="6"/>
          <FormattedText X="25" Y="9" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="CENTER" Color="#ED7300" BackgroundColor="#164516" Bright="Yes">
                <Color Value="#A1A9A6"/>     
            <String>%DTO%</String>
          </FormattedText>
        </Element>
    </Element>
    <Element>
      <Visible>(L:TypEntry) 2 ==</Visible>   
        <Element>
          <Position X="170" Y="6"/>
          <FormattedText X="25" Y="9" Font="Tahoma" FontSize="8" LineSpacing="9" Adjust="CENTER" Color="#ED7300" BackgroundColor="#164516" Bright="Yes">
                <Color Value="#A1A9A6"/>     
            <String>%REP%</String>
          </FormattedText>
        </Element>
    </Element>

The Hot spot to cycle is on screen.

I also added another on screen click hot spot to display a advisory notation.
Occasionally when you conduct a google search for a specific Lat/Long you get a return that has the prefix as a + or - instead of an alphabet character,
this pop up grey square acts as a decode.

The following shot shows the ADD..DTO..REP cycle.
Whatever is showing up as orange text indicates that any of the 5 lines will be entered into the flight plan in that manner.
fsx 2013-04-17 00-50-46-37.jpg

This instrument ended up being much better than I originally envisaged.

Cheers
Karol
nTGMF.jpg
 
Last edited:
Back
Top