• 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.

FSXA EventID

Roy Holmes

Roy Holmes

Resource contributor
Messages
1,805
Country
us-virginia
Modeldef has umpteen references to EventIDs. Like <EventID>0x00011204</EventID>

Is there a list of these somewhere?

Roy
 
Right in the main SDK docs, there's a document labeled EventIDs. These list the named ones. The numbered ones you see are not documented because they are designed for comunication between 3D VC gauges and XML or C gauges. They are designated by individual gauge developers, and so you're not going to find a list of the numbers, I'm afraid.
 
Thanks,
It was the numbered ones I was interested in since I could find no reference to them in the SDK. I do not use the ACES XML system, but it does seem to use numbered EventID's.

In another post you said you used a Schema for XML and I'd be interested in knowing about that. I took the FS9 DTD and have added many sections. I sometimes come across something it calls invalid, which I know works, so I change the DTD accordingly.

Roy
 
When we talk about FSX versus the FS9 schema, it's just the way the code is written.

FS9 uses a slightly different version of the FS XML, which is slightly looser and easier to work with, although there are a couple of functions which are present in the FSX scheme which are not in the FS9 scheme. FS9 code works in both FSX and FS9, so there are quite a number of people who only use FS9 to ensure cross-compatibility. The differences are in things like capitalisation of tags and case-sensitivity.

I always use the FSX scheme, because I only program for FSX, and it also allows me to open my gauges in the ACES editor to work with - which some people do, and some people couldn't care less about.

As an example, have a look at this current thread for some comparisons between the two:

http://www.fsdeveloper.com/forum/showthread.php?t=71166

You can see how although the code is essentially the same, it is 'formatted' differently.

If there are official schemas/DTD's for the FSX version, I haven't seen any, but that doesn't mean they don't exist...
In fact scratch that, there is one in the Panel and Gauges SDK folder/PropDefs. Just remembered.:)
 
I'm mainly talking gauge code not modeldef structure/syntax. Propgauge.xml details are covered in the XML gauges SDK. Propsimvar is pretty skinny!

I use XMLSpy for editing gauge code and it has really useful features that will prompt you for the code to enter as well (in conjunction with the DTD) as telling you if your file is invalid when you try to save it or "pretty pretty" it. Because I have embedded XML maps in some of my gauges, I have had to add reams of stuff to the DTD because without that Spy will stop checking for errors when it finds something not in the DTD.

I can edit modeldef with it because I do not invoke the DTD in those circumstances. Good editor, was originally free, but I had to buy my current version.

Thanks for the insight

Roy
 
Interesting. Since I bought Visual Studio 2005 Standard Edition (mainly for C, C++, GDI+ gauge work), and discovered the marvelous XML Editor that came with it, that what I use exclusively.

It automatically uses whatever .dtd's it can find. One of the really neat feature is "Intellisense" that will auto-fill the <ClosingTag> for me...

and highlights possible syntax errors with "squiggly underscore lines" to make 'em stand out like a Las Vegas beacon! :D
 
The thing I usually get wrong is the nested "Element close Element" structure. Spy lets you hide the code between Elements and gives a very clear structure to work out where the close elements should be.
Horses for courses as my Dad (a jockey) used to say
Roy
 
Visual Studio will do the same thing. Next to every <Update> or <Element> tag there is a [+] sign in the left column. Clicking on the [+] symbol will collapse the entire section to this:

Code: 
[+]  <Element>...

I use this feature often, especially with very large XML scripts. After a complete section of script is completed and debugged, I collapse them so I don't have to scroll 13,000 lines up or down to find stuff! :)
 
ot: is it possible to make VS remember the rollout state of XML files?
 
You must log in or register to reply here.
Back
Top