Announcement

Collapse
No announcement yet.

Menu position (for multimonitor)

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Menu position (for multimonitor)

    Hey CDR, jcdillin and I have been wondering about getting the menu to pop up in a different screen position.

    Say, for example, that someone had a normal TS with their frontend running and a second screen with no TS and the GPS maps on and wanted the menu to pop up on the TS screen.

    Is there any way to define the menu position via skin or setting file?

    Also, I would need things like the zoom and menu button to be on the lower skin so can these commands be sent using something like send-keys to FD or would we have to go the route of embedding FD into the frontend and using an 800x960 skin that covers both screens with the GPS map in the top one (along with stuff like track names and the speed and compass)?

    To be hoest i will probably have FD running all the time so embedding it will probably be the best route but the position of the menu is my initial main concern.

    Cheers

    Andy

  • #2
    Hey Scouse,

    With regards to the menu, not sure.

    To the second part - FD can be spoken to using the COMSend stuff which is native within Road Runner and can control FD via the RR skins, I don't use an FD skin anymore as I have it embedded within RR and it controls all the FD functions.

    Comment


    • #3
      Originally posted by Scouse Monkey
      Hey CDR, jcdillin and I have been wondering about getting the menu to pop up in a different screen position.

      Say, for example, that someone had a normal TS with their frontend running and a second screen with no TS and the GPS maps on and wanted the menu to pop up on the TS screen.

      Is there any way to define the menu position via skin or setting file?

      Also, I would need things like the zoom and menu button to be on the lower skin so can these commands be sent using something like send-keys to FD or would we have to go the route of embedding FD into the frontend and using an 800x960 skin that covers both screens with the GPS map in the top one (along with stuff like track names and the speed and compass)?

      To be hoest i will probably have FD running all the time so embedding it will probably be the best route but the position of the menu is my initial main concern.

      Cheers

      Andy
      I could stick the menu up on another sceen, but you would still become a cropper when it comes down to route inputing, theres no way of inputing a route other than having either a ts or a mouse. Most of the quick menu things like view . day . night can be used via the sdk

      CdR
      Follow me on Twitter

      http://www.FreeICE.co.uk

      Comment


      • #4
        hmm bugger this is gonna take some thinking about as I wont be able to reach the GPS screen!

        I guess i could have a button to switch the clone screen mode...hmmmm.....

        what about if i made FD 800x960 (ie 2 screens high) but made the bottom half of the skin transparent (can you use gif files for skins?)

        Then I make the menu input screens for addresses, favourites transparent on the top half.

        Could that work?

        Also, i could then make other parts on the top screen transparent so certain features of the frontend show through.

        Problem is that FD would have to come to the front whenever you needed to input hmmmm

        (yeah i am just writing down ideas here)

        Gareth, when you embed FD do you place the buttons somewhere else? and do the address/favourite/POI menus pop up in the GPS window?

        Comment


        • #5
          ooo what about having the option to duplicate the GPS screen on the lower map so you can input stuff? and then have it close and leave the main GPS screen?

          Damn i need to learn to program!

          Comment


          • #6
            so you cannot tell the OSK and the streets window to come up in a diffrent location other than on top of FD?
            肚子笑痛了
            S60 Install

            Comment


            • #7
              Well you can surely use the windows OSK instead

              Comment


              • #8
                Originally posted by jcdillin
                so you cannot tell the OSK and the streets window to come up in a diffrent location other than on top of FD?
                the osk and address input is FD.. its in the same form. What there is which may help you is a resize sdk command.. you could have a input gps skin in RR that moves FD buy using the resize:0:0:800:600 then you could auto move it back once the input is done.. just a thought

                CdR
                Follow me on Twitter

                http://www.FreeICE.co.uk

                Comment


                • #9
                  Input GPS skin sounds like what i need. But i guess i would have to move the map down to the lower screen when inputting and then have it move back up to the top screen when navigating. That is no big problem and could actually work quite well.

                  ~I will just fill the gap where the GPS screen was with "inputting destination" or summit. Could look quite cool

                  Comment


                  • #10
                    Originally posted by Scouse Monkey
                    Well you can surely use the windows OSK instead

                    oh yeah, typing on that is fun
                    肚子笑痛了
                    S60 Install

                    Comment


                    • #11
                      Originally posted by jcdillin
                      oh yeah, typing on that is fun
                      well use a different windows OSK!

                      Comment

                      Working...
                      X