Sign in to follow this  
martinlest2

How to open panel windows >No.9?

Recommended Posts

Hi. In FS9, how can I open panel windows which appear in the panel.cfg file as [window.10] and above? Of course 'Shift+10" is not an option.. I have made a lot of xml gauges to create different icons which I can put in the cockpit to open panel windows as far as no.9 (with different bmp files associated with them, for different functions) but again, anything above no.9 does nothing in practice.

 

In other words, if my Garmin GPS is window.15 and I cannot shift window numbers around in the panel.cfg file to accommodate it (some payware a/c panels stop working if you do that of course), how to open the GPS window in FS?

 

Thanks!

 

Martin

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

I'm not sure if there is a way to do it with keyboard commands, but if you use the Views menu at the top, then go to Instrument Panel, all the different windows should be listed there.  If you don't see the menu bar at the top, press Alt first.  That should bring it up.

Share this post


Link to post
Share on other sites

I have made a lot of xml gauges to create different icons which I can put in the cockpit to open panel windows as far as no.9 (with different bmp files associated with them, for different functions) but again, anything above no.9 does nothing in practice.

Hi, Martin,

 

Not at my FS computer right now, but there's a line called something w/ ID= in it

for each window. If you assign a unique numerical code in that line (create the whole line

if necessary) you can assign that ID in your xml icon gauge.

 

If this doesn't make sense, I'll find an example.

 

Mike

Share this post


Link to post
Share on other sites

 

 


Hi. In FS9, how can I open panel windows which appear in the panel.cfg file as [window.10] and above? Of course 'Shift+10" is not an option.. I have made a lot of xml gauges to create different icons which I can put in the cockpit to open panel windows as far as no.9 (with different bmp files associated with them, for different functions) but again, anything above no.9 does nothing in practice.

 

This is the complete icon gauge (except for the separate bmp file):

-------------

<Gauge Name="Radar_Icon" Version="1.0">
   <Image Name="radar_icon.bmp"/>
   <Mouse>
      <Tooltip ID="TOOLTIPTEXT_TOGGLE_RADAR"/>
      <Cursor Type="Hand"/>
      <Click>219 (>K:PANEL_ID_TOGGLE)</Click>
   </Mouse>
</Gauge>
-----------

 

Clicking on this gauge's associated bmp image (pasted onto another panel window) will open the following window:

------------------

[Window16]
file=..\RADAR ORIG COLORS.bmp
visible=0
Background_color=0,128,64
size_mm=343,475
ident=219
window_pos= .358,.708
position=0
gauge00=F16!Radar,16.0066666666667,54.88,306.413333333333,310.413333333333
gauge01=F16!Radar Mode, 38.8733333333333, 416.173333333333, 73.1733333333333, 27.44
gauge02=F16!Radar Range,116.62,416.173333333333, 73.1733333333333, 27.44
 

Note that the number in Ident=219 is the same as the one in the gauge entry

      <Click>219 (>K:PANEL_ID_TOGGLE)</Click>

 

Mike

Share this post


Link to post
Share on other sites

Thanks for the replies - and especially the example! I am not a very advanced xml 'programmer' to say the least so was not aware of this - I'll try it out later today..

 

I so wish I had asked this question years ago!!!

 

Martin

Share this post


Link to post
Share on other sites

 

 


I am not a very advanced xml 'programmer' to say the least so was not aware of this - I'll try it out later today..

 

I got the template from someone else, I didn't write the gauge myself.

 

This should also work if you use one of the stock FS IDs, such as RADIO_STACK_PANEL or GPS_PANEL instead of a made-up number.  Changing these to a number might have some unexpected result.

 

Do you have an example where an xml icon gauge opens a window by window number?  I don't know how to write it that way.

 

Mike

Share this post


Link to post
Share on other sites

Another possibility  is to have a  a 3 in 1 Icon

<Gauge Name="Radar_Icon" Version="1.0">
   <Image Name="radar_icon.bmp"/>
  <!-- 3 in 1 Icon --> 
   <Mouse>
   <Macro Name="Button1">
        (M:Event) 'RightSingle' scmp 0 == if{ 219 (>K:PANEL_ID_TOGGLE) } 
        (M:Event) 'MiddleSingle' scmp 0 == if{ 342 (>K:PANEL_ID_TOGGLE) }
    	(M:Event) 'LeftSingle' scmp 0 ==  if{ 784 (>K:PANEL_ID_TOGGLE) }</Macro>  
        <Area> 
            <Tooltip>R Radar M GPS L Throttle</Tooltip> 
            <Click Kind="LeftSingle+MiddleSingle+RightSingle">@Button1</Click>
            <Cursor Type="Hand" />
        </Area>
   </Mouse>
</Gauge>	

As the tool tip indicates :-

- Left click for Radar window

- Middle click for GPS window

- Right click for throttle

 

Your relevant click code for your desired Window is placed within the  "if" brackets.

 

The idents  219 , 342 , 784  above are examples only .

In the above Window text it was;

ident=219

and it Must match your Icon script.

 

The 3 in 1  Icon could just as easily be a 2 in 1 that uses only Left and Right clicks.

<Gauge Name="Radar_Icon" Version="1.0">
   <Image Name="radar_icon.bmp"/>
  <!-- 3 in 1 Icon --> 
   <Mouse>
   <Macro Name="Button1">
        (M:Event) 'RightSingle' scmp 0 == if{ 219 (>K:PANEL_ID_TOGGLE) }
    	(M:Event) 'LeftSingle' scmp 0 ==  if{ 784 (>K:PANEL_ID_TOGGLE) }</Macro>  
        <Area> 
            <Tooltip>R Radar L Throttle</Tooltip> 
            <Click Kind="LeftSingle+RightSingle">@Button1</Click>
            <Cursor Type="Hand" />
        </Area>
   </Mouse>
</Gauge>

Cheers

Karol

Share this post


Link to post
Share on other sites

Mike, the xml gauges look like this - this one is called Panle5 and supposedly opens "window 5" (which in practice is window 4, as there is no zero):

 

<Gauge Name="Panel5" Version="1.0">
   <Image Name="Icon_Throttle.bmp" ImageSizes="19,19,30,30"/>
   <Mouse>
      <Tooltip>Throttle Panel</Tooltip>
      <Cursor Type="Hand"/>
      <Click>14200 (>K:PANEL_5)</Click>
   </Mouse>
  </Gauge>

 

I then add a gauge= line to the Window.00 (or wherever) that reads:

 

gaugexx=XMLGauges!Panel5, xx,yy,18,18

 

.. I am sure you know the ropes!

 

The text you gave works fine in opening up panels above no.9. Thanks again for posting.

 

Edit: Only saw your post Karol after I sent this reply. Will have a look at that too, though it seems more complex to achieve the same result. Thank you.

Share this post


Link to post
Share on other sites

Another possibility is to have a a 3 in 1 Icon

 

 

Thanks very much Karol.  I didn't know how to do this (I only have a two-click mouse but as you said certainly it could be made to work w/ two clicks).

 

 

Mike, the xml gauges look like this - this one is called Panle5 and supposedly opens "window 5" (which in practice is window 4, as there is no zero):

 

<Gauge Name="Panel5" Version="1.0">

   <Image Name="Icon_Throttle.bmp" ImageSizes="19,19,30,30"/>

   <Mouse>

      <Tooltip>Throttle Panel</Tooltip>

      <Cursor Type="Hand"/>

      <Click>14200 (>K:PANEL_5)</Click>

   </Mouse>

  </Gauge>

 

 

 

Thanks for your example.  One question: what does the number "14200" do, since the window you want to open is already identified by "Panel_5"?

 

Mike

 

 

 

Share this post


Link to post
Share on other sites

That's the ident in the panel.cfg, but I think you can put anything, or nothing, there, since the window is defines, as you say...

Share this post


Link to post
Share on other sites

That's the ident in the panel.cfg, but I think you can put anything, or nothing, there, since the window is defines, as you say...

  

 

No ! !

 

That ident number is critical to the function of the Icon switch.

 

The ident number in your Icon switch must  be exactly the same as the number in the following line of your Window detail,

 

ident=14200

 

Cheers

Karol

Share this post


Link to post
Share on other sites

Yes ! ! ! (Three exclamation marks outdoes your two, especially in LOUD BOLD TYPE)... Did you mean to sound so aggressive? I am sure not  :rolleyes:

 

I have lots of such gauges in my FS setup and when you specify a window, the ID is irrelevant because the information you write as to window number overrides the ID. Several of the xml files (as I was lazy and just copied and edited them) have exactly the same ID, which in no way matches the ID in the panel.cfg and they all open their respective, and different ,windows just fine.

 

If you don't specify a window, then I agree... as per the example that Mike posted. In that case the ID is crucial, but not in my examples. I've been making these gauges for ten years... believe me...

 

Regards.....

Share this post


Link to post
Share on other sites

Not aggressive , just emphasis.

I have used bold type to draw emphasis to specific portions of replies that other wise might be missed.

I am not the combative sort of person.

I must admit that this is the very first time that I have got this sort of reaction.

 

How are you 'specifying' the window within the Icon switch ?

 

Cheers 

Karol

Share this post


Link to post
Share on other sites

Exclamation marks, capital letters and Bold type are the internet equivalent of shouting, that's common knowledge, but it's OK, as I said, I was pretty sure that wasn't how it was meant (and added a smiley to show it!). ^_^  There! There's another one...

 

The icon switch (in the panel.cfg I assume you mean) is just a normal gauge line. For instance, where XMLGauges is my folder, within FS9/Gauges, and the xml file, for example, is Panel8.xml, and the next free gauge is 55...

 

Gauge55=XMLGauges!Panel8, xx,yy,18,18

 

.. usual xx,yy co-ordinates of course.

 

The gauge itself is as in Post#8, above,

 

Cheers Karol,

 

Martin

Share this post


Link to post
Share on other sites

Martin

 

Thanks for the above.

 

In your Icon  code

<Gauge Name="Panel5" Version="1.0">
   <Image Name="Icon_Throttle.bmp" ImageSizes="19,19,30,30"/>
   <Mouse>
      <Tooltip>Throttle Panel</Tooltip>
      <Cursor Type="Hand"/>
      <Click>14200 (>K:PANEL_5)</Click>
   </Mouse>
  </Gauge>

Is it the  5  that specifies that  " window5 "  will be called up to be visible ?

 

I have never seen this used before , it looks interesting.

 

Cheers

Karol


Thanks very much Karol.  I didn't know how to do this (I only have a two-click mouse but as you said certainly it could be made to work w/ two clicks).

 

Mike

 

Originally I thought that my mouse was only 2 clicks , Left  single click and right single click.

Then I discovered that you can depress the mouse wheel and that that action is the  Middle single click.

 

I have recently created instruments that make use of :-

Left  single click

 Middle single click

right single click

mouse wheel up

mouse wheel down

 

Cheers

Karol


 

Share this post


Link to post
Share on other sites

(>K:PANEL_5) .. that's the one that opens the window, but you can't go beyond 9. You can specify a different bitmap and save as a different file name of course. The first line contains that name...

 

This just produces the icon to call up the window - whether the window is visible by default or not (if that is what you meant) is specified in the panel.cfg file

Share this post


Link to post
Share on other sites

Martin 

 

Thanks , that's an interesting alternative , I had only known of the old ident method ,

as they say ... you learn something new every day .

 

Cheers

karol

Share this post


Link to post
Share on other sites

If you don't specify a window, then I agree... as per the example that Mike posted. In that case the ID is crucial, but not in my examples. I've been making these gauges for ten years... believe me...

Unfortunately, that is not completely accurate. The fact that it "sort of works out anyway" is not really relevant. Checking the SDK is a good place to look.

 

<Click>14200 (>K:PANEL_5)</Click>

 

The command "PANEL_5" does one, and only one thing: "Toggles panel 5", in other words [Window04].

 

The number in red (14200) does nothing at all. It doesn't hurt anything, it is simply ignored.

 

For the most part, only EventID tokens that end in _SET take input variables or constants. Well, there are a couple of exceptions to this, but aren't there always some exceptions? :wink:

 

Well, as it happens PANEL_ID_TOGGLE, PANEL_ID_OPEN, and PANEL_ID_CLOSE are a few of the exceptions. To be perfectly fair though, the SDK is quite wrong in the descriptions for those three commands though when it states that they only affect the indexed panels (1--9).

 

They will actually take any ID number one chooses to use, provided the same number is defined in the [Windownn], ident=nnnn entry.

 

Suppose I wish to create an entry to open/close this entry:

[Window10]
size_mm=245,190
window_size = 0.6, 0.5
position=3
visible=1
ident=11111
//gauge00=B350Engines!LocalVarsLogger,  0,0,245,190

I have defined this [Window10] to use the ident number 11111, so this would be the command for that number:

<Click>11111 (>K:PANEL_ID_TOGGLE)</Click>

BTW Karol, the ident= method is the newer method. ^_^

Share this post


Link to post
Share on other sites

Unfortunately, that is not completely accurate. The fact that it "sort of works out anyway" is not really relevant. Checking the SDK is a good place to look.

 

14200 (>K:PANEL_5)

 

The command "PANEL_5" does one, and only one thing: "Toggles panel 5", in other words [Window04].

 

The number in red (14200) does nothing at all. It doesn't hurt anything, it is simply ignored.

 

 

Bill, I think you and Martin are in agreement: if you use the Panel_X method you don't need an ID number in the gauge (corresponding to the Ident= line for that window in the panel.cfg file).  The window is determined by the Panel_X value for X.  But if you use the PANEL_ID_TOGGLE (or I presume PANEL_ID_OPEN or PANEL_ID_CLOSE) method in the gauge, you do need the number from Ident=.  For Karol's multi-use icon method, you need the Ident numbers for all three windows.

 

 

 

To be perfectly fair though, the SDK is quite wrong in the descriptions for those three commands though when it states that they only affect the indexed panels (1--9).

 

 

Yes, I noticed that and it's also true in the FSX SDK. 

 

 

Thanks , that's an interesting alternative , I had only known of the old ident method ,

 

as they say ... you learn something new every day .

 

 

I did too!  Regarding the middle click, I only have a two click mouse w/ a track ball - no wheel.  Is there a way for me to get a middle click?

 

Mike

Share this post


Link to post
Share on other sites

martinlest2, on 02 May 2015 - 7:23 PM, said:snapback.png

If you don't specify a window, then I agree... as per the example that Mike posted. In that case the ID is crucial, but not in my examples..

 

'n4gix', on 04 May 2015 - 12:08 AM, said:snapback.png

Unfortunately, that is not completely accurate. The fact that it "sort of works out anyway" is not really relevant.

 

Hi.. Not sure which bit of that is 'not completely accurate' or (moreover) why the fact that it works is 'not really relevant'. As I said, when you specify a window to toggle, then the ID number has no function. You go on to say the same thing more or less Bill. The fact that it works is the most relevant thing, for me! :P  I could (perhaps 'should') have edited the ID numbers out, for neatness, but in practice, it's the 'same difference', as they say.

 

So yes, Mike, I think Bill and I are basically in agreement.

 

Martin

Share this post


Link to post
Share on other sites

Yes, I noticed that and it's also true in the FSX SDK. 

 

I did too!  Regarding the middle click, I only have a two click mouse w/ a track ball - no wheel.  Is there a way for me to get a middle click?

Unfortunately, track balls won't press down...

 

One of the most glaring omissions from the SDK (all of 'em including P3Dv1 and P3Dv2) is mention of the ability to send an indexed variable to the smoke system!

 

Two conditions must be preset for this to work:

  1. at least one engine running
  2. default 'smoke system' enabled

With those two conditions met, then one may toggle on/off up to 98 'smoke channels'. Even better, those channels may be used to trigger any effect .fx file!

 

So, one could have the first six 'smoke channels' assigned to colored smoke (for an airshow?), and more lights than one could reasonably need...

 

To turn 'on' smoke channel 11 one does this:

11 (>K:SMOKE_ON)

To turn it 'off' one does this:

11 (>K:SMOKE_OFF)

 

For example, here is the smoke system for the Milviz T-38A implementing a "progressive smoke trail" tied to the engine's afterburner power from min to max:

[SMOKESYSTEM]
smoke.1 =-17.20,  -0.83,  0.54, MilViz_T38A_ABurner
smoke.2 =-17.20,   0.83,  0.54,  MilViz_T38A_ABurner
smoke.3 =-18.60,  -0.83,  0.54, MilViz_T38_BurnerStage1
smoke.4 =-18.60,   0.83,  0.54,  MilViz_T38_BurnerStage1
smoke.5 =-18.60,  -0.83,  0.54, MilViz_T38_BurnerStage2
smoke.6 =-18.60,   0.83,  0.54,  MilViz_T38_BurnerStage2
smoke.7 =-18.60,  -0.83,  0.54, MilViz_T38_BurnerStage3
smoke.8 =-18.60,   0.83,  0.54,  MilViz_T38_BurnerStage3
smoke.9 =-18.60,  -0.83,  0.54, MilViz_T38_BurnerStage4
smoke.10=-18.60,   0.83,  0.54,  MilViz_T38_BurnerStage4
smoke.11=-16.90,  -0.83,  0.54, MilViz_Fire1
smoke.12=-16.90,   0.83,  0.54,  MilViz_Fire1
Hi.. Not sure which bit of that is 'not completely accurate' or (moreover) why the fact that it works is 'not really relevant'.

I suspect what I should have written was that it is somewhat misleading, because that particular set of commands doesn't require nor take an indexed input constant.

 

But yes, with that one caveat Martin, we are in agreement.  :Applause:

Share this post


Link to post
Share on other sites

Great. I love threads with a happy ending!! :Applause:

 

Just as a heads up, there's a nice 'smoke' (actually more of heat/shimmer) effect, (http://www.flightsim.com/vbfs/fslib.php?searchid=36420700), but that goes into the [Lights] section. I have had it installed in almost all my jet a/c since it was uploaded in 2006. (I have a long list of co-ordinates for the aircraft.cfg if anyone is interested).

 

M.

Share this post


Link to post
Share on other sites

Hi. In FS9, how can I open panel windows which appear in the panel.cfg file as [window.10] and above? Of course 'Shift+10" is not an option.. I have made a lot of xml gauges to create different icons which I can put in the cockpit to open panel windows as far as no.9 (with different bmp files associated with them, for different functions) but again, anything above no.9 does nothing in practice.

 

In other words, if my Garmin GPS is window.15 and I cannot shift window numbers around in the panel.cfg file to accommodate it (some payware a/c panels stop working if you do that of course), how to open the GPS window in FS?

 

Thanks!

 

Martin

The above is the initial  post of this thread.

 

Some very interesting stuff above.

 

But .... the thread starter wanted access to greater than 9 windows.

 

As far as I am aware there are only 3 methods to do that .

 

1. In the older style 2D and VC cockpits you could place as many "Hide/Display Icons" as you wanted or could fit in your panel , however you must use

the  'ident'  in the Icon to go over  the 9 window limit that applies to either ,  

 

- the keyboard approach

  or

- the  panel_5 type approach

 

The newer 3D style cockpits have the panel as a part of the actual aircraft/cockpit model.

We do not have access to the source code that covers those panels , thus it is virtually impossible to modify or customise 

the panel by adding extra Icons.

 

The following Methods 2 and 3 enable this obstacle to be overcome by hi jacking one or more of the Icons

that exist in the 3D style panel.

Replace an existing Icon with one of your own based on the following,

 

2. create an  "2 in 1" or "3 in 1"  Icon as shown earlier in this thread , that one icon will give you access to 2 or 3 Windows.

    if the panel you are dealing with had 6 Icons , then replacing them with 6 of "3 in 1" Icons gives you access to 18 Windows.

 

3. another method while not so convenient is to use one of the existing Icons to call up a utility Window.

    The utility Window would have a BITMAP that might have for example 35 Icons on it's surface.

     That gives you access in that example to 35 Windows.

 

      The utility Window can be either,

       => 35 Icons to call the 35 Windows

          or,

      => 35 On/Off instrument switches that would populate the current Window with instruments that you desire. This is

           similar to "MiniPanel" created by Bill McCellan.

 

So there are some options available.

 

Cheers

Karol

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this