This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 89350 - a11y: Shift-F10 does not bring up context menu on Connector link
Summary: a11y: Shift-F10 does not bring up context menu on Connector link
Status: VERIFIED FIXED
Alias: None
Product: uml
Classification: Unclassified
Component: Diagram Collaboration (show other bugs)
Version: 5.x
Hardware: All All
: P2 blocker (vote)
Assignee: Kris Richards
URL:
Keywords: A11Y
Depends on:
Blocks: 90350
  Show dependency tree
 
Reported: 2006-11-15 01:59 UTC by Peter Lam
Modified: 2006-12-01 00:32 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
NPE on shift+F10 for connector (2.62 KB, application/octet-stream)
2006-11-22 11:09 UTC, Andrew Korostelev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lam 2006-11-15 01:59:08 UTC
Repro Steps:
- create a collaboration diagram
- add and name 2 lifeline elements
- connect the 2 lifeline elements with the Connector link
- select the Connector link
- press Shift-F10 and no menu pops up
Comment 1 Andrew Korostelev 2006-11-22 11:08:36 UTC
attached NullPointerException appears in ide-coco-061121_17.
Comment 2 Andrew Korostelev 2006-11-22 11:09:27 UTC
Created attachment 36203 [details]
NPE on shift+F10 for connector
Comment 3 Kris Richards 2006-11-27 19:03:53 UTC
Forced TestBedMenuManager.getLocation() to return (0,0) if the location had not been set. As is the case 
when the popup menu is displayed via accelerator.
Comment 4 Peter Lam 2006-11-28 08:13:56 UTC
verified in build 061127_12
Comment 5 Trey Spiva 2006-11-30 16:52:51 UTC
I had to revert the change, because it caused another problem.
Comment 6 Trey Spiva 2006-11-30 17:07:16 UTC
I have made the connector link behave correctly when the mouse location is not valid (i.e. null).  The 
problem is that when you use the keyboard to open the context menu, you do not have a valid mouse 
location, so null is being returned.  So, the original solution was just to default to return a mouse location 
of [0,0].

That does not work for nodes like the class.  In this case, we need to know that the context menu is being 
opened by the keyboard, not the mouse.  So, when the mouse location is not valid, it also adds menu item 
for the list compartments (add attributes, and add operations are added).  When we default point [0,0] the 
draw engine can not determine if this location was generated by the mouse, or because of a keyboard 
event.
Comment 7 Peter Lam 2006-12-01 00:32:08 UTC
verified in build 061130_7.