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 255360

Summary:	[81cat] Alternative KeyMap doesn't works if the keymap list is filtered
Product:	editor	Reporter:	-Silver-
Component:	Completion & Templates	Assignee:	Dusan Balek <dbalek>
Status:	NEW ---
Severity:	normal
Priority:	P3
Version:	8.1
Hardware:	PC
OS:	Windows 8 x64
Issue Type:	DEFECT	Exception Reporter:
Attachments:	IDE log

Description -Silver- 2015-09-17 11:03:14 UTC

Product Version = NetBeans IDE Dev (Build 201509150002)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0_66-ea
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.66-b02

Reproducibility: Happens every time

STEPS:
1. Open Tools->Options->KeyMap  
2. Type anything into the "Search:" field to filter the list of keymaps. (ie type "fix")
3. A filtered list is shown (in our case there is FixCode.. between the entries).
4. Click on the button "..." on the left of an entry and select "add alternative" 
5. Insert a Key shortcut for the alternative.
6. Click on Apply

ACTUAL:
The full keymap list is shown again and the alternative shortcut doesn't respect the key selecte

Comment 1 -Silver- 2015-09-17 11:03:18 UTC

Created attachment 156239 [details]
IDE log

Comment 2 Jiri Prox 2015-09-17 21:56:01 UTC

Can you please provide more detail? I'm sorry but I don't quite understand what is this issue about. 

I'v tried adding alternative shortcut when the list was filtered and it wored fine.

Comment 3 -Silver- 2015-09-21 12:28:05 UTC

(In reply to Jiri Prox from comment #2)
> Can you please provide more detail? I'm sorry but I don't quite understand
> what is this issue about. 
> 
> I'v tried adding alternative shortcut when the list was filtered and it
> wored fine.

Hi Jiri, 
sorry for the delay.
The problem was that the new (alternative) key combination sometime was not saved and the key combination list reported an empty cell for it. 
Btw I tried again to reproduce it today and seems that the issue has been fixed in the last build (in general seems that the key binding option panel is many more stable with this build and also other issues/exceptions thrown are not reproducible anymore).  

Thanks and best regards,


--
Giuseppe Tino