[Gameking1Duke]

So, I was trying to make an app that was on a single .mobi file with the outermost element being a multipage, and everything else under it be a page or a multipage. I decided to do this because for some of the things I was implementing, it became difficult to generalize for dynamic cases if they weren’t in the same .mobi file (namely that the id prefixes were different for elements within differing .mobi files). After a while of developing, I noticed that at certain levels deep into the multipage, the phonui.gotoMultiPage function was not working and I realized that only the top level multipages were visible (i.e when you pick the showPage function for a button, it only showed the top level multipages, which meant that it could not actually access pages from lower level multipages). In this case, there is no use for the phoneui.gotoPage function because it is all on one screen, but the phoneui.gotoMultiPage function does not always work.

I was wondering if this was something that was explicitly not supported by MobiOne or if there is another way to get around this problem.

[support-octavio]

Hi,

How deep are you nesting multipage widgets. When we initially developed it we discussed preventing layering mulitpage widgets due to some really tricking implementation challenges. I’m not aware of any other mobile widget framework that supports such nesting. A single level of nest (an MP inside an MP) should be supported. Beyond that and I would not be surprised if there are functional issues. Can you share an example project that demonstrates the issue(s) you are experiencing for our dev team to analyze?

[Author]

Posts