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

Application Versions/Builds and identifying them...

iangbusa

iangbusa

Messages
223
Country
us-ohio
Hi Arno

Happy New 2016!! :D

I know you and I may have "talked" about this before but most recently it's come back to bite me a couple of times and caused a couple of hiccups. I'm just whining about a minor niggle so push this to the bottom of the "things to think about" list.

The topic, in part only, applies to all the tools - ModX, scenProc, etc. There's very comprehensive coverage of updates on the "Recent changes" page which I monitor and track carefully, quite regularly downloading updates of the relevant tools. I understand that the Development release download links will incorporate the last change as documented on the Release database.

So my main "query":
  • For any of the applications, I wondered if there's any way (clearly these are just "nice to haves" and in no way critical) to have release [ID] information on the download file
For example, would it be possible to have a version ID or even date/time. Right now I rename them when saving to my online "repository" but, um, I'm decidedly lazy o_O and also would like to save each one with an "official" version/build ID of some sort so I know I'm not downloading a duplicate and just renaming to a new ID of my own invention. I think you explained before there's some difficulty in doing this (auto-generation of download file?) but I can't recall why.​

Other than that, when I try to see which version I'm actually running (I have 'em all over the place and use different ones if I come across things newer ones don't seem to do quite the same as an older one might!):
  • ModX has an About dialog which provides really useful information on the Version, Build (I think), and Date (but no Version information added to App Window title).
  • The Application Window for scenProc does show a version (e.g. 1.1.0.0) but that's about as much as I've seen. However, I can't find an About dialog giving a little bit more detail as does the one for ModX. I think FXEditor has neither.
  • Small niggle, as I said. And it's :peanut::peanut::peanut: compared to all the incredible stuff your work does and the value it provides!! Have I expressed my appreciation recently? :)
Er, um, one other thing - another little issue, I guess... I can't get my scenProc to point to or bring up the pdf Manual in its Application folder when trying through the "Show Manual" button. Any thoughts?

Cheers!!

ian
 
Hi,

scenProc should show the revision number in the title bar as well, so that you have the same information as in the MCX about dialogue.

About the download filename, for me it's easier to keep it constant. Else I would have to update the webpage every time. Now it's all nicely automated the entire build.
 
Thanks, Arno.

Now I recall that was what you mentioned before. It's no trouble really to keep control of installers at my end (with a bit of willpower and common sense - both of which I'm often lacking!). scenProc does show the version in the title (e.g. v1.1.0.0) but there is no "About" dialog with detailed Build information as there is with the others (e.g. MCX About with Version 1.4.0.0 c88c237 DEV 1/1/2016) - or at least I can't find one. And strangely I can't get the manual to pop open when I click on Show Manual. I have no idea why - it's just a standard install and running from a Taskbar short-cut pointing at the install folder.

No worries on any of this. Not at all important.
 
I think this might be a configuration setting on my build server that's wrong. Let me check.
 
Hi,

I have fixed the configuration issue, now the revision is shown in the title bar as well (as it was intended).

About the manual, it is assumed the PDF file is in the same folder as the EXE. Then the button should load the PDF in your PDF viewer. If nothing happens the PDF file was not found.
 
The new development release is build at 4:00 in the night (my time zone). So when you posted it wasn't online yet.
 
And now that you mentioned it, I didn't get an email from the new build. So let me check the build server.
 
Ok. Your software is extremely useful and really appreciate the work you are doing.

I'm looking forward to further functions to make scenery even more complex and believable.
 
I have triggered a new build now, but some tests failed. So it might be corrupt. I'll double check when I get home tonight.
 
I have fixed the issue that made the build perform weird, so in about 10 minutes a new development release will be online that will be working OK again.
 
You must log in or register to reply here.
Back
Top