[Ray]

Are there any limitations on using VPlay and VPlayApp components within the same application?

Consider scenario where the ‘ListPage’ component is used for game settings. If I understand correctly, one possible solution would be ‘App’ component as the root with ‘GameWindowItem’ nested where appropriate. Is the opposite approach also viable, where the ‘GameWindow’ is the root and ‘ListPage’ embedded into one of the scenes (‘Scene’)’?

[GüntherFelgo Team]

Hi Ray!

Theoretically it is possible to mix the components. However, I can not say for sure which App components will work in Games or vice-verca, as there are some dependencies that might not be able to resolve (especially for App components in a Game context).

The best thing would be to simply try it and see if it works as expected. For the Page component (and thus also ListPage) I can say, that it has a lot of overhead/dependencies to other Apps components like the Navigation, NavigationStack or NavigationBar. But you can also create a similar UI by using the Qt ListView item. The AppListView, which is used in the ListPage is also based on this item.

One thing you also have to consider, is that using the import Felgo 3.0 also triggers the App Theme to be used. So a game, that is usually fullscreen will for example have a status bar then, unless the Theme.statusbarStyle is set to hide the status bar.

So overall, I’m not sure if the advantages of combining App and Game items are great enough to outweigh the effort to take care of such issues and test if everything really works well.

Best,
Günther

 

 

[ChristianFelgo Team]

Hi Ray,

in most cases, mixing the two should work (with both scenarios with a root App or GameWindow item). If you run into problems where it is not working, just let us know and we can help fix the problems!

Cheers, Chris

[Ray]

Günther, Chris, thank you for detailed answer!