Visual defect: 'Everything' in the search dialog

[AntonyD]

i do not need to count clicks. i do need to use ergonomic and fully visible gui elements.
these elements for which you suddenly decided to count clicks are used once and for ever. one time i set all checks and after that use search files context. practice - long-long practice shows that there is no sense to change checked states of these elements.
hence you notice about counts is not useful, sorry.

ALL other parts of this new design from Lefteous are awesome!

[TW]

personally i'm still waiting for some check button "everything RAW" search... typing ev: as a prefix is annoying.

[phantom]

i do not need to count clicks. i do need to use ergonomic and fully visible gui elements.
these elements for which you suddenly decided to count clicks are used once and for ever. one time i set all checks and after that use search files context. practice - long-long practice shows that there is no sense to change checked states of these elements.
hence you notice about counts is not useful, sorry.

ALL other parts of this new design from Lefteous are awesome!

I agree with you. Lefteous design looks really nice and clear.

[Horst.Epp]

+1 for Lefteous design

[phantom]

Only the default font (german language) fits to the search dialog.

Is it possible to increase the width of the text search fields?

Look at screen shot!

Image: https://abload.de/img/search3uj7h.png

[AntonyD]

Is it possible to increase the width of the text search fields?

exactly that is why we here is asking ghisler to hear us - and to implement much more effective design from Lefteous OR
provide us for evaluation a brand new version of this dialogue from the author's position.
Current changes which we made "24.08.16 Fixed: Search dialog: Move 'Everything' checkbox to the right of the packer checkbox if it doesn't have enough space (32/64)" cannot be in any way useful and good for the end user.

[Sob]

If I'm looking correctly, what Lefteous did was (from top):

1) Made "Drives" button wider and "Search in" combo shorter. I don't think that's improvement.

2) Rearranged following three lines of items up to separator. This looks much better than original. I never understood why shortened "RegEx" checkbox was put on the left, when there's plenty of space on the right for it, and with proper description. And this new jumping "Everything" checkbox joke, I'm affraid I just don't get it. If nothing else, implement at least this.

3) Grouped encoding options under one button. I agree that it might make things worse if someone uses these option very often. The question is, does anyone do it? I for one checked all four the first time it was possible and don't plan to touch them ever again. Because when I search for something, I usually have no idea which encoding the file uses, except that these days it's probably not ASCII/DOS. But aside from button, I do like the logical grouping, i.e. that these four options belong together and are not just part of long list of different options like all others.

4) Extended description of "Plugins" checkbox and moved its settings to the right. Button at the right is definitely better, because it's how UI usually works. Longer text looks nice, but perhaps someone might find it misleading, if they don't have the proper plugins.

[Lefteous]

2Sob

1) Made "Drives" button wider and "Search in" combo shorter. I don't think that's improvement.

The idea here was to align the folder browse/drive button with the internal text search button. Some kind of imaginary row.

Because when I search for something, I usually have no idea which encoding the file uses, except that these days it's probably not ASCII/DOS.

Yes, that's why I opened a new thread which just about the text search: http://ghisler.ch/board/viewtopic.php?t=45475

[j7n]

Of course the menu button is just a button with a dynamic label. I was confused by the transparent visual style and thought it was some other control.

I normally just leave ANSI and Unicode options checked, to permit me to search both 8-bit and Unicode strings in mixed-format "binary" files, such as EXE and DLL. I also do not usually search for non-English text from TC, so I can also find UTF this way. It might be inconvenient for someone who switches the options often.

I think with all options a search is marginally slower, probably not a concern for anybody, since it is also i/o bound, and it could also return false results for short strings.

[Lefteous]

So as many agree here that the encoding options are something that is set once and then forgotten why not put it to the configuration dialog instead? There would have to be a link to that page in the search though.
For me the Everything option is another candidate. Users could still be notified about the possibility in a message.

[Dalai]

I'd like to call the attention to saved searches. In which way are they important? Actually, I also check the options Unicode and ANSI to search for text only once. This is fine until you load some saved search. If you do, Unicode gets reset, so the next time you do a regular search for Unicode and ANSI (i.e. without loading a saved search), you have to make sure the options are checked. This is tedious, but hiding the encoding stuff under some menu button would make things worse. Putting them somewhere in TC's configuration wouldn't work either because sometimes I want to search for Unicode but NOT for ANSI (or the other way around).

Regards
Dalai

[AntonyD]

... If ... Unicode gets reset, so the next time ... you have to make sure the options are checked.

but the provided design shows this moment. don't you see it?
ALL checked variants are get listed in this new "combobox" element
http://savepic.ru/11179226.png
pay attention of the red arrow's end point.

hence if you suddenly got Unicode|ANSI|ASCII reseted - you can easily to find out it.
there is even no needs to open this pseudo combobox. All values are on front of this element - in its main area.

[Dalai]

2AntonDudarenko
True, but that won't help with checking the encodings again. This is where Ghisler's answer comes into play - more clicking.

Regards
Dalai

[AntonyD]

more clicking

I should consider this as a joke, sorry.
How many tabs this dialog contains?
How many clicks i should make for saving search results?
for setting dates for search, for setting plugin's additional searching params. Many-many clicks.
But this is not a main problem - because all these elements are not vital for the search process.
That's why we can allow for ourselves to do not calculate clicks for achieve of desired goal of search.