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

scenProc suggestion for lines of a single step

Clutch Cargo

Clutch Cargo

Messages
1,636
Country
unitedstates
As my scenProc scripts become more complex the individual steps are also becoming longer. May I suggest:
1. add a symbol to break a step into two or more lines. I believe they call this a continuation symbol. I've seen such symbols as '\' like in Python.
2. If one resizes the scenProc window if it gets smaller than a line's length, the code will work like a word-wrap so one can see the entire step.
scenProc - need wrap around.jpg
 
Last edited:
Hi,

Would one of the two work? They seem to approaches to the same problem to me.
 
I think it gives the option for the developer. Resizing the scenProc window is a quick & easy way to see everything as one moves about the script, where adding a continuation symbol is a deliberate decision to alter the look of the script. I can't say which is better... maybe what is easier to code to try first?

Just thinking, this could look very "messy" for lack of a better word at the moment. What about a deliberate intent of say 5-6 characters per line should one resizes or uses a symbol? The key would be it indents until the next Step has begun. I think this would keep the script looking cleaner and easier to read where you could easily see a new step is beginning like so:

If one just had a simple wrap-around - not so clean and easy to read:

ExportOGR|FTYPE="LINE" AND (fclass="motorway" AND popValue="over4000") OR (fclass="motorway" AND popValue="over2000") OR (fclass="motorway" AND popValue="over1000") OR (fclass="motorway" AND popValue="over500")|ESRI Shapefile|B:\CA\Section_63\Roads\CA_BX46_motBase.shp|ALL
ExportOGR|FTYPE="LINE" AND (fclass="motorway" AND popValue="over4000") OR (fclass="motorway" AND popValue="over2000") OR (fclass="motorway" AND popValue="over1000") OR (fclass="motorway" AND popValue="over500")|ESRI Shapefile|B:\CA\Section_63\Roads\CA_BX46_motCombo.shp|ALL
ExportOGR|FTYPE="LINE" AND (fclass="motorway" AND popValue="over1") OR (fclass="motorway" AND popValue="over10") OR (fclass="motorway" AND popValue="over50") OR (fclass="motorway" AND popValue="over200")|ESRI Shapefile|B:\CA\Section_63\Roads\CA_BX46_motSplashRoad.shp|ALL

If one would have automatic indents with wrap-around or symbol based on Steps.

scenProc - indent wrap around.jpg


Thoughts?
 
Let me throw in one more request... not trying to get nickpicky - it's more of a convenience request. It's just in the results panel I have to reset the column widths after every time I run a script. It would be nice if the columns of Time and Sender (why it's called Sender and not Step?), would automatically adjust its width to the longest number of characters in that column. I look at the Sender column a lot to see if certain steps were performed. Ok... enuf begging 🙄
 
It's called sender because it's a generic event log. MCX uses the same component and there are no steps in MCX.

It might be an idea to have the sender name always visible, although I try to use as much space as possible for the event itself. I think the column width is just a simple percentage at startup right now.

As for the multi libe steps, i think that would just complicate the validation and parsing. Maybe some word wrap would be possible.
 
You must log in or register to reply here.
Back
Top