Custom menu items may cause timeline items to appear to have updated

[GoogleCodeExporter]

Using custom menu items may unexpectedly trigger notification tones or sort 
bundle sort order changes.

This occurs in XE11, but will be fixed in XE12.

What steps will reproduce the problem?
1. Create a timeline item with a custom menu item
2. Trigger the custom menu item on Glass

What is the expected output? What do you see instead?
- The timeline item should stay where it is
- No tone should be heard

Please use labels and text to provide additional information.
- The timeline item moves to the front of the bundle, or the front of the 
timeline
- A notification tone is heard

Original issue reported on code.google.com by mimm...@google.com on 13 Nov 2013 at 1:54

[GoogleCodeExporter]

According to the issue description, this was to be fixed in XE12 but is not 
mentioned in the XE12 release notes. Is there any update?

This is a major headache for my use case, wherein a slide deck is sent from 
Google Drive to Glass, and the Glass acts as a remote control. i.e. swiping to 
a slide in the deck and using the custom menu item "present" causes that slide 
to show on the presentation screen. This bug causes that slide to also be sent 
to the beginning of the bundle, causing the user to lose their place within 
their deck. You can see this happening with the app at 
http://yourshow.superhumanlabs.com

Cheers!

Original comment by ash.eldr...@gmail.com on 18 Dec 2013 at 4:49

[GoogleCodeExporter]

It looks like it didn't make it into XE12. It's indeed still happening.  Other 
than that I don't really have much to update. It'll be fixed in a future 
release.

Original comment by mimm...@google.com on 18 Dec 2013 at 7:20

[GoogleCodeExporter]

Original comment by mimm...@google.com on 20 Dec 2013 at 5:24

• Added labels: log-12244960

[GoogleCodeExporter]

Any update on this issue?

Original comment by da...@davidstallard.com on 26 Apr 2014 at 6:48

[GoogleCodeExporter]

Can we please get a status update? This is marked as high priority and stated 
to be fixed in XE12. We are now on XE17.

Original comment by ash.eldr...@gmail.com on 13 Jun 2014 at 12:26