Page 1 of 1

[TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-06, 16:09 UTC
by white
Create this saved search named "FindComment" to search file comments only:

Code: Select all

[searches]
FindComment_SearchFor=
FindComment_SearchIn=>
FindComment_SearchText=CommentToSearch
FindComment_SearchFlags=0|000002000020|||||||||0000||||Comment

[SearchCustomField]
0exts=*Comment:*
0fields=[=tc.comment]
Create this button to open the search window and load the FindComment search:

Code: Select all

TOTALCMD#BAR#DATA
LOADSEARCH FindComment

wcmicons.dll,47



-1
  • Click the button
  • The option "ANSI charset (Windows)" is checked (bug)
  • Go to the Load/Save tab and load the search "FindComment"
  • The option "ANSI charset (Windows)" is not checked (good)

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-06, 17:02 UTC
by Horst.Epp
Here in both cases ANSI charset (Windows)" is checked ?

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-06, 18:07 UTC
by white
Horst.Epp wrote: 2022-11-06, 17:02 UTC Here in both cases ANSI charset (Windows)" is checked ?
There seem to be more issues depending on your last search.
You should get the result I described when you do the steps exactly as I mentioned.

If you load the search "FindComment" on the Load/Save tab and "ANSI charset (Windows)" isn't cleared, load it a second time.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-06, 18:41 UTC
by Horst.Epp
white wrote: 2022-11-06, 18:07 UTC ...
If you load the search "FindComment" on the Load/Save tab and "ANSI charset (Windows)" isn't cleared, load it a second time.
Ok, in this case its cleared.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-06, 19:21 UTC
by petermad
I can confirm the bug.

But try this:
1. Restart TC
2. Open the find Files dialog and load the saved "FindComment"
3. The "Ansi charset (Windows)" is checked.
4. Load the saved "FindComment" one more time.
5. The "Ansi charset (Windows)" is no longer checked checked.

It does not seem to be of any importance whether the "Comment" search plugin is enabled, but "Plugins" has to be enabled in the search dialog.

Notice that it is not possible to clear ALL options in the "Find text" section, if I try, the "Ansi charset (Windows)" will always automatically be checked.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-08, 16:33 UTC
by ghisler(Author)
That's probably happening because the dialog box automatically checks "Ansi charset" when nothing is selected.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2022-11-08, 17:29 UTC
by petermad
That's probably happening because the dialog box automatically checks "Ansi charset" when nothing is selected.
But something is selected: "Plugins" - which is apparently not recognized the first time the saved search is loaded, but IS recognized the second time.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2023-05-03, 19:20 UTC
by ghisler(Author)
This should be fixed in TC 11 beta, please test it.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2023-05-04, 08:47 UTC
by petermad
2ghisler(Author)
1. Restart TC
2. Open the find Files dialog and load the saved "FindComment"
3. The "Ansi charset (Windows)" is checked.
4. Load the saved "FindComment" one more time.
5. The "Ansi charset (Windows)" is no longer checked checked.
The above still happens in TC 11.00b1 - see: https://tcmd.madsenworld.dk/findcommentsearch.mp4

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2023-05-04, 09:01 UTC
by white
Confirmed. Bug with LOADSEARCH is fixed, bug with loading a saved search in the Find Files dialog isn't.

Re: [TC10.52] LOADSEARCH enables ANSI charset option when it shouldn't

Posted: 2023-05-04, 09:28 UTC
by ghisler(Author)
That's why I request that you create a separate bug report for each bug! I didn't notice that there was a second report in this thread, sorry. :(