Author Topic: B3: Find / Look In: being reset to Current Buffer  (Read 600 times)

PiezonTM

  • Senior Community Member
  • Posts: 122
  • Hero Points: 7
B3: Find / Look In: being reset to Current Buffer
« on: September 08, 2017, 05:33:48 pm »
The "Find" / "Look in:" is changing from "<All Buffers>" and then resets back to "<Current Selection>".

To reproduce the problem:
  • Do a search using the "Find and Replace" dialog and use the "Find" tab and select "Look in:" set to "<All Buffer>" and do a search.
  • Do a search using the same dialog box except run a "Find in Files" search.
  • Do a search using the same dialog box except go back and select the "Find" search.  At this point the "Look in:" is now set back to "<Current Buffer>"; used to stay on "<All Buffers>".

Not sure if this is a new feature or bug; however this was not the same on previous versions.

SlickEdit Pro 2017 (v22.0.0.3 64-bit)

Serial number: FE17393_BETA
License type: Beta License
License expiration: 2017-11-06 19:00:00
License file: /opt/slickedit-pro2017beta3/bin/slickedit.lic

Build Date: September 04, 2017
Emulation: CUA

OS: Linux
OS Version: Ubuntu 16.04.2 LTS
Kernel Level: 4.10.0-32-generic
Build Version: #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017
Processor Architecture: x86_64

X Server Vendor: The X.Org Foundation
Memory: 39% Load, 8839MB/22622MB Virtual
Shell Information: /opt/slickedit-pro2017beta3/bin/secsh -i
Screen Size: 1920 x 1080, 1920 x 1080

Project Type: Single file project - Other
Language: .js (JavaScript)
Encoding: Automatic

Installation Directory: /opt/slickedit-pro2017beta3/
Configuration Directory: /home/tmoore/.slickedit/22.0.0/
Migrated from: /home/tmoore/.slickedit/21.0.3/
Spill File: /tmp/$slk.tmoore.27145



Lee

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 1284
  • Hero Points: 128
Re: B3: Find / Look In: being reset to Current Buffer
« Reply #1 on: September 08, 2017, 06:31:35 pm »
Thanks for the report.  Reproduced, and it shouldn't be doing that.  I will investigate and fix that for next beta drop.