The screens are a little odd at the moment, you can only navigate through them using certain pathways as the <pick> animations for the soft buttons are not done yet. This is something I was working on yesterday, and will do more on today - it's not actually a big job, just copying and pasting with concentration.
I hope by next week I'll have posted at least my updates to the central MFD, with accurate WPT and FREQ pages (these will look as much like their real life counterparts as possible, although will work slightly differently because of the limitations of FG and my coding) and all the buttons working the way they should.
With these jobs come a couple of decisions to be made regarding navigation and communications, which I'd like Almursi's opinion on (well, I'd like everyone's opinion, but devs particularly). According to the manual, the aircraft navigates using its LINS (Laser Inertial Nav Sys), GPS and TACAN - there is no NAV radio capability for ILS like you'd find in an airliner: effectively, it does not use civilian solutions. Also, it has ACTive and StandBY TACAN settings, which default FG Radio dialog does not have, and the radio comms is totally different. I therefore suggest a dedicated Typhoon Comms dialog, like the dedicated AP, with only realistic options.
This dialog would NOT feature NAV1 or NAV2 radios, but it would have two TACAN entries, active and standby, and channel selection similar to that in the real aircraft - eight preset radio channels (editable in an .xml file in the aircraft's directory) and two manual channels (the equivalent of COM1 ACT & SBY). These channels are available to both radios (called RAD1 and RAD2 in the Typhoon, instead of COM1 and COM2). I'm going to make a demo of this to show you, and I hope you'll agree it's more realistic within the existing FG framework to omit the things the real aircraft doesn't have.