When searching for registers in the register pane, some of the items in the filtered results become unresponsive when clicking on them. They should transition to a highlighted state upon clicking, as they normally do, but this doesn't happen for some of the items in the result set.
Example:
In the example above, I searched for "stack" and then clicked on the "SP" item - no visual feedback, the item did not transition into a highlighted state. Interestingly, this does not seem to affect the double click action (to open the register inspection window), or the context menu trigger. Same happens when I click on the "CPU" register group (second item). But not when I click on the "CPU" peripheral (first item) - in that instance, the item appears highlighted.
I suspect the problem is somewhere in the ListScene widget. Start with debugging the item position value in the mousePressEvent() handler.
I doubt this is specific to any target, but just in case: I was using the ATmega32A in the above example.
This is a low priority bug. Not sure when I'll get to it.
When searching for registers in the register pane, some of the items in the filtered results become unresponsive when clicking on them. They should transition to a highlighted state upon clicking, as they normally do, but this doesn't happen for some of the items in the result set.
Example:
In the example above, I searched for "stack" and then clicked on the "SP" item - no visual feedback, the item did not transition into a highlighted state. Interestingly, this does not seem to affect the double click action (to open the register inspection window), or the context menu trigger. Same happens when I click on the "CPU" register group (second item). But not when I click on the "CPU" peripheral (first item) - in that instance, the item appears highlighted.
I suspect the problem is somewhere in the ListScene widget. Start with debugging the item position value in the
mousePressEvent()handler.I doubt this is specific to any target, but just in case: I was using the ATmega32A in the above example.
This is a low priority bug. Not sure when I'll get to it.