SDK Mapping Changes - Adjustments reuqired
Dear SDK Users
With the upcoming release 0.49.x there will be a little change in the SDK which I would like to bring to your attention since there might be slight changes required for your drivers before that release.
We are adjusting a small number of mapping so that these follow our standard wording. Here are the ones which will be changed:
SKIP BACKWARD will now be called PREVIOUS
SKIP FORWARD will now be called NEXT
ENTER will now be called CURSOR ENTER
If you are using any of these three legacy mappings in your driver, you should go ahead and change these now. In the currently available release 0.48.35 both mappings do work, so you can go ahead and change these without waiting for the next release.
If you are already using these mappings, no change is required.
You have to re-add your driver to the NEEO Brain after changing the driver so that the changes will be applied.
Let me know if you have questions.
Patrick
-
Hi Patrick
Do we need to reinstall the SDK and if so how?
Reply -
Patrick When using the predefined Button Groups, this should not be neccessary? Or?
Reply-
The button groups are not affected, no changes required if you use button groups
Reply
-
-
What happens to those that keep their “old” driver installed? Will these commands be name changed on the brain?
Reply-
If you do not update the SDK driver and leave the current devices on the Brain as is, the commands will still work if explicitly used in shortcut. However some widgets will no longer be detected (for example the control pad will not be available if CURSOR ENTER is missing).
If you update the SDK driver but do not remove and re-add the device on the Brain, the widgets will not be detected anymore (same as above). In addition to that the mapping will be wrong so the Brain will have commands that the SDK driver does not recognize, and the SDK driver will expect commands that the Brain does not know about. (This could be mitigated on the SDK side by keeping both the new and the old command for the same action)
Reply
-
-
Patrick
Just to be clear - PREVIOUS/NEXT/CURSOR ENTER will work in 48.35+. SKIP BACKWARD/SKIP FORWARD/ENTER will only work up to but not including 49.x (at which time they will not work)?
In future, would be nice if you deprecated commands for a few firmware before removal - gives time for people to make adjustments (and gives time for those adjustments to trickle down to all people).
Reply-
Tim Roberts I'll talk about that with our developer team, in general I agree that there should be a phase for such changes covering more than just one firmware release.
Reply
-
-
Hi Patrick it would be great to if we could do without re-add the driver. I have some higher level stuff that uses deviceId for example...
Reply-
Morgan Fromentin That is a general "feature" which we want to add to the SDK. Basically meaning that it would no longer be needed to re-add a driver/device if you do changes. That should also speed up the development process. An according story has been filed.
Reply -
Patrick
That would be most excellent (channeling my inner bill & ted voice here)
Reply
-
-
Patrick Somehow i already had NEXT, PREVIOUS and CURSOR ENTER in my code since day one. now I'm confused
Reply-
Niels de Klerk Both of these worked previously, we removed "older" ones and therefore these do not work any longer.
Reply -
Patrick thanks, That was a small change on my part.
Reply
-