that's what I meant when I spoke about cloning pages. Turbo's argument is valid though: what do you show in full screen mode then?
I tend to like Henrik's solution apart from the active element on the map. I fly in the west of Germany - which is full of airspace restrictions. I barely manage to hit the right airport when I tap on the screen (usually it takes me a few attempt to get to see the right information). Adding an active map element to an already fairly cluttered screen is not something I like (and one of the main reasons I stopped using LK8000). At least on my streak info boxes are pretty large (and have no underlying airspace information anyway) so hitting a Navbox is easy. I would suggest a slight modification to Henrik's approach. Make the "standard" (i.e. those on the top line of Henrik's example) link together. Tapping on any one of them will cycle to the next target (in the example going from task to nav1 to nav2). And all "standard" nav boxes (i.e. those not specifically tied to task, nav1 or nav2) would switch the target and of course the map. Everything else I would do in the same way as Henrik described it. my 2 cents Torsten Am 16.01.2013 um 16:55 schrieb Claus-W. Häbel <c...@online.de>: > Hi, not that bad, but > > What about just creating a new Infobox-Page for that?? > > The screeen wouldn't be so cluttered and the info would be awsome easy > to detect and everything else could be placed be at their proper site ... > > if you don't need ist just let it be empty .. > > We do have 8 (eight!) InfoBox Pages !!! > I'm using 2 of them in my flights .. > > Wouldn 't be that a very easy idea?? > > claus > > > > > > > > > > Am 16.01.2013 12:25, schrieb Henrik Bieler: >> Hey all, >> >> I tried to visualize my suggestion of navigation modes. >> The result, which took me a lot of time, (even tough it does not quite >> look like it did.... ) can be seen in the attached pdf. >> If you like the concept, or at least part of it, I could attach it to a >> ticket, or start a new one. >> >> http://www.alice-dsl.net/h3v/xcsoar_modes.pdf >> >> @Torsten: >> I thought about your concern of screen cluttering. And therefore also >> included your proposed "active infobox". >> IMO it is importat for the concept that the active mode is displayed >> somewhere. I would prefer the screen corner, >> but why not let each user choose... :-) >> >> Cheers Henrik >> >> ------------------------------------------------------------------------------ >> Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery >> and much more. Keep your Java skills current with LearnJavaNow - >> 200+ hours of step-by-step video tutorials by Java experts. >> SALE $49.99 this month only -- learn more at: >> http://p.sf.net/sfu/learnmore_122612 >> _______________________________________________ >> Xcsoar-user mailing list >> Xcsoar-user@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/xcsoar-user >> > > ------------------------------------------------------------------------------ > Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery > and much more. Keep your Java skills current with LearnJavaNow - > 200+ hours of step-by-step video tutorials by Java experts. > SALE $49.99 this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122612 > _______________________________________________ > Xcsoar-user mailing list > Xcsoar-user@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/xcsoar-user
------------------------------------------------------------------------------ Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612
_______________________________________________ Xcsoar-user mailing list Xcsoar-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcsoar-user
