[Csantucci]

In ORNYMG 109.2 a new control, specifically devoted to the loading of the background (static) part of screen pages has been made available: ORTS_STATIC_DISPLAY. Its way of working has been added in the first thread of the post.

@akioyamamura: I don't understand why you need more states. In reality only one is needed, and I have created the ORTS_STATIC_DISPLAY control for that.
Every screenpage has its own static part, and for each of them an ORTS_STATIC_DISPLAY control has to be generated, that contains in line ORTSScreenPage the name of the related screen, and has as .Ace file only that specific static part.

[akioyamamura]

This new funcionality is exactly what I need. Thank you Carlo!

https://youtu.be/6yBgBabjFtg

[Csantucci]

At the moment the strings within the parentheses of ORTSScreenPage and ORTSNewScreenPage must have only lowercase characters. This limitation will be removed in next release of ORNYMG.

[Csantucci]

The restriction has been removed in ORNYMG 109.4.

[cjakeman]

Serana, on 02 November 2021 - 12:25 AM, said:

I had something even more ambitious in mind: https://blueprints.l...js-cab-controls

Basically, you would define a place on the 2D or 3D cab as a screen which will display the content of an HTML page with JavaScript (to make it interactive with the simulator).
That way, you can really customize what you want to display on the screen.

That's basically how screens work in Microsoft Flight Simulator.

James and I have talked this over and we don't think this approach is appropriate right now.

A lot of work would be needed (and I believe Microsoft had lots of problems with their initial rollout). There is also the common problem of publishing controls which use features within OR which cannot then be improved without breaking content.

These issues are not insurmountable, so perhaps we can revisit the idea later when we come to create our own cab view format.

[Serana]

cjakeman, on 23 November 2021 - 11:27 AM, said:

James and I have talked this over and we don't think this approach is appropriate right now.

A lot of work would be needed (and I believe Microsoft had lots of problems with their initial rollout). There is also the common problem of publishing controls which use features within OR which cannot then be improved without breaking content.

These issues are not insurmountable, so perhaps we can revisit the idea later when we come to create our own cab view format.

I will do a proof of concept anyway. I don't think it is really that difficult.
And about breaking content... come on, that's a subject we already have with C# scripts and it's not that problematic currently.

[Csantucci]

Following Chris' approval of the blueprint, a PR to the official OR release for this feature has been generated.

[Csantucci]

The feature has been fully approved and will be present in next official Testing release.

[Csantucci]

Feature now available in Testing release T1.4-100 and in ORNYMG 112.

[trainagrandevitesse]

Good evening,
is there a maximum number of names for "ORTSScreenPage"?
I use 12 different "ORTSScreenPage" names, everything works.
But from 13 names of "ORTSScreenPage" all "ORTS_STATIC_DISPLAY" and associated "ORTS_SCREEN_SELECT" buttons disappear.

I tried several possible combinations but I always get the same result.

Good night

Jean Prisca