Managing multiple screen pages on a display in 2D and 3D cabs
#21
Posted 08 November 2021 - 01:34 AM
@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.
#22
Posted 08 November 2021 - 06:22 AM
#23
Posted 10 November 2021 - 12:03 AM
#24
Posted 11 November 2021 - 01:50 AM
#25
Posted 23 November 2021 - 11:27 AM
Serana, on 02 November 2021 - 12:25 AM, said:
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.
#26
Posted 23 November 2021 - 12:55 PM
cjakeman, on 23 November 2021 - 11:27 AM, said:
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.
#27
Posted 12 December 2021 - 02:46 AM
#28
Posted 14 December 2021 - 08:44 AM
#29
Posted 17 December 2021 - 01:35 PM
#30
Posted 11 September 2022 - 03:28 PM
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