Microsoft MCE drivers - secondary commands

Hello,

Except if I am wrong, secondary commands (long press)  are not implemented for Microsoft MCE drivers. Can you please set that up ASAP?

The minimalist touchscreen UI supports so few items due to your design that secondary command is a nice way to improve usability until a decent and more configurable UI is released.

Thank you in advance

Reply
5replies Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • Yann FREMONT That a thing Andy or Fäbu are responsible as well. They will come back as soon as they have more Information. Keep in mind, that they work during swiss business hours and therefor it can take a bit longer now, because it is weekend.

    Reply Like
  • Hi,  Yann FREMONT. Thank you very much for your request. I've checked this with the driver team, and unfortunately, we are not able to offer an IR code for the long press as this is software related. There is already this voting for additional hard button functionalities and customization. Please vote there as this will also cover your needs for the Microsoft MCE driver. 

    Reply Like
    • Ingrid Hi. Thank you for the reply. Yes I already voted but does not seem in the plan.

      Isn't there a way for developer to assign whatever IR to the long press for Microsoft MCE standard so I can remap them to different function on my own?

      Or isn't it possible to have the same behavior as for the the Microsoft MCE advanced driver: when holding a hard key presses, my IR receiver logs a first IR code S11000010xxxxx corresponding to the command followed by a flow of S0 IR codes until the key is released. Why can't this be implemented the same for Microsoft MCE standard driver?

      Reply Like
    • Hi, Yann FREMONT. I'm sorry if I misunderstood you.

      You said:

      The minimalist touchscreen UI supports so few items due to your design that secondary command is a nice way to improve usability until a decent and more configurable UI is released.

      First of all, I'm wondering if you have already tried to create your own shortcut screen by adding shortcuts and widgets and hiding not required UI slides. In that way, you can create your own user interface for often used commands. Have you already tried that? 

       

      Or isn't it possible to have the same behavior as for the Microsoft MCE advanced driver:


      Did I get that right that you meant the advanced Microsoft MCE driver on your NEEO? If that's the case, which secondary commands did work for you exactly? Also, what specific commands are you looking for? 

      Reply Like
  • Hi @Ingrid

    Ingrid said:
    First of all, I'm wondering if you have already tried to create your own shortcut screen by adding shortcuts and widgets and hiding not required UI slides.

     Sure I did. But:

    First, widgets and shortcuts cannot be customized. No way to change icon or labels which makes custom slide barely unusable for home users (and ugly!)

    Second, I purchased a Neeo (and my current Nevo S70 and prior remotes) because there are hard buttons which allow convenient control without looking and navigating on a screen. Otherwise, I would stick to one of the many apps available on smartphone that do the job (including the UI of my current OpenHAB home automation server). Hard keys and IR beaming are the main (and only?) advantages of a remote over smartphone so please promote and develop this!

    Ingrid said:
    Did I get that right that you meant the advanced Microsoft MCE driver on your NEEO?

     I use the "Microsoft MCE driver standard". Unlike the "Microsoft MCE driver advanced", it does not send IR while maintaining hard key pressed. It would be nice if it behaved the same.

    Ingrid said:
    Also, what specific commands are you looking for? 

     For example:

    Button Back could map to Back on press and Home on long press

    Button Menu could map to ContextMenu on press and DvdMenu on long press

    Button Ch+/Ch- should map to Ch+/Ch- (PgUp/PgDown) on press and (Prev/Next) on long press (they are currently mapped to rew/ffw which is nonsense)

    Other mapping can be considered but not sure they will fit to everyone's use. It is just important to have click/long press or even double click mapped to commands so they can be used (remap for targeted software if needed). At least, repeating on key hod would allow me to detect long press. That is also why I emphasize on allowing end-users remapping the keys so everyone can adjust to its needs.

    Reply Like
Like Follow