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 198697 - When the edit/find "window" is open, it's impossible to go to the search and replace window, you have to close the search window first before
Summary: When the edit/find "window" is open, it's impossible to go to the search and ...
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: Search (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
: 192429 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-05-18 07:43 UTC by bunam
Modified: 2011-09-21 12:31 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bunam 2011-05-18 07:43:17 UTC
Product Version = NetBeans IDE 7.0 (Build 201104080000)
Operating System = Mac OS X version 10.6.7 running on x86_64
Java; VM; Vendor = 1.6.0_24
Runtime = Java HotSpot(TM) 64-Bit Server VM 19.1-b02-334
Comment 1 Marian Mirilovic 2011-05-18 09:10:46 UTC
Could you please write exact steps to reproduce and reopen this issue ? Thanks in advance.
Comment 2 bunam 2011-05-18 09:17:28 UTC
Open the  edit/find menu

The "incremental search side bar" is opened

then do the menu item edit/replace

then nothing happen 

you have to close the "incremental search side bar"

before calling the menu item edit/replace that open the replace window
Comment 3 Milutin Kristofic 2011-08-10 14:10:14 UTC
Yes, you need to have your focus to a text editor, not in find text field. A shortcut also doesn't work. This will be repaired with a new replace bar.
Comment 4 Milutin Kristofic 2011-08-24 12:40:55 UTC
There is a new find/replace ui and it is possible and recommended to use it from searchbar by its shortcut or from menu.
Comment 6 Milutin Kristofic 2011-09-21 12:31:33 UTC
*** Bug 192429 has been marked as a duplicate of this bug. ***