SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => Topic started by: rowbearto on December 22, 2022, 02:08:29 AM

Title: BigFind Replace window not hiding when start the replace
Post by: rowbearto on December 22, 2022, 02:08:29 AM

In BigFind I go to replace tab, enter stuff into "Search For:" and "Replace with:" and click "Replace".

The BigFind window is not hiding itself after this.

Then I get the "Prompt Replace" window and I want to see the editor window where it highlights an instance of search and replace. But its getting blocked by the BigFind window so I can't see it.

I'm using 27.0.1.0 64bit Qt4, linux x64

I did not try a clean config, using my config. Maybe it also happens in a clean config too?

Title: Re: BigFind Replace window not hiding when start the replace
Post by: Dennis on December 22, 2022, 12:56:57 PM

Check the following settings:

Tools > Options... > Editing > Search > Tool Window Options > (x) Close after find/replace

Tools > Options... > Appearance > Tool Windows > Find and Replace > (x) Esc dismisses floating window

Title: Re: BigFind Replace window not hiding when start the replace
Post by: rowbearto on December 22, 2022, 07:53:39 PM

Both of those options were already checked yet I have this problem.

I uploaded my user.cfg.xml to support, look for user.cfg.rowbearto_221222.xml

Title: Re: BigFind Replace window not hiding when start the replace
Post by: Clark on December 22, 2022, 11:13:55 PM

This appears to be a new bug in 27.0.1. I can reproduce this with a clean config. We will look into this.

Title: Re: BigFind Replace window not hiding when start the replace
Post by: Clark on December 23, 2022, 12:14:14 AM

Hot fix added for this. You can load the attached macro to fix this bug.

Title: Re: BigFind Replace window not hiding when start the replace
Post by: rowbearto on December 23, 2022, 03:35:57 AM

Thanks Clark!

Where is the best place to put the tbfind.e ?

In the past I used a .e file I downloaded from here but then several updates of SlickEdit later it was using my downloaded .e file instead of the one that came with the update. I would like to prevent that in the future?

Title: Re: BigFind Replace window not hiding when start the replace
Post by: Clark on December 23, 2022, 03:48:44 AM

There’s no perfect place for it. When you get the hot fix, it will be replaced by the the hot fix version. Hot fixed are less prone to errors because of the versioned state file.

Title: Re: BigFind Replace window not hiding when start the replace
Post by: rowbearto on December 23, 2022, 04:54:52 AM

Well in the past a 'compile.e' file that I had locally (probably from some post here) was overriding what was in the SE install/hostfix see:

https://community.slickedit.com/index.php/topic,18897.msg75643.html#msg75643

Would like to prevent this from happening again.

Title: Re: BigFind Replace window not hiding when start the replace
Post by: Clark on December 23, 2022, 03:01:09 PM

Are you sure you didn't load this other "compile.e" after the hot fix was installed? I don't think this can happen any other way. Only files added to def_macfiles are automatically loaded when there is a new state file. "system" macros are not added to def_macfiles. You can check this variable after you load tbfind.e

Title: Re: BigFind Replace window not hiding when start the replace
Post by: rowbearto on December 24, 2022, 01:27:44 AM

I don't remember anymore about the compile.e file.

However very recently I copied one of my macros, lets call it rowbearto.e to a new directory. I loaded the newdir/rowbearto.e in Slickedit (load command) but it still was using the .ex file from olddir/rowbearto.ex. I was able to know this because it was still exhibiting old behavior that was changed in the newdir/rowbearto.e.

I had to explicitly remove the olddir/rowbearto.ex to force it to use newdir/rowbearto.e, then it behaved as I expected.

So I'm worried about a similar issue if I load your macro, even though I very much want this fix.

I think I'll create an 'sepatch' directory where I place these and then I can easily move that directory to make sure SE doesn't use them.