Bug 12298 - Selection wrong after scrolling
: Selection wrong after scrolling
Status: CLOSED FIXED
Product: SqueezePlay
Classification: Unclassified
Component: UI
: unspecified
: PC Windows XP
: P1 major (vote)
: 7.4.0
Assigned To: Wadzinski Tom
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-06 23:35 UTC by Philip Meyer
Modified: 2009-10-05 14:34 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Meyer 2009-06-06 23:35:37 UTC
There is a problem where invoking the context menu on an item actually brings up the context menu for the wrong item.

Follow these steps:

1. flick-scroll a long list
2. whilst it is scrolling, long-touch an item to bring up the context menu for it
3. Press back, then long-touch a different item

The original item is highlighted and brings up the context menu, rather than the new item.
Comment 1 Richard Titmuss 2009-07-27 01:13:53 UTC
Reset priority before triage.
Comment 2 Wadzinski Tom 2009-08-06 11:35:23 UTC
 == Automatic comment from SVN commit #6946 to Repository: jive ==
https://svn.slimdevices.com/jive?view=revision&revision=6946

Fixed Bug: 12298
Description:
- touch on flick stops the current flick, doesn't allow press nor hold. Thought this might have been a CM issue, but was not....
worktime: 1


 == Modified 1 files total ==
7.4/private-branches/fab4/squeezeplay/src/squeezeplay/share/jive/ui/Menu.lua
Comment 3 James Richardson 2009-10-05 14:34:32 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.