That’s true. Also true, I never once mentioned popups. My proposal (above) and my solution (other thread) solves the problem without use of
Popups have no part to play and are not part of this subthread of discussion. Nor does the solution deal with touchscreens, previously dismissed by @pmario (rightly).
Sorry, but I’m finding it really hard to follow your train of thought. 
I’ll back off now.
Right. But I think @Mohammad was/is in popup mode?
Just a side-note caro
TT
If you’re saying his head is in popup mode, well, I can’t fix that 
It feels like bait and switch sitting here. I’m sure that’s not what he’s trying to do, but that’s how it feels (ooh, feelings on a tech forum, whatever next!)
If you’re saying his UI is presented in a popup, that shouldn’t matter one jot. The CSS can be adjusted easily to constrain the output accordingly.
Good! I think some check is worth it since the rest of the system depends on it being accurate?
Just a comment
TT
I believe he has gone @saqimtiaz, with some validity IMO, that popups in TW need a JS salve yet to be fully adaptable.
You may hit my whicket if I’m off caro.
TT
What I was looking is showing field value in a tooltip (it is subclass of popup windows). To be clear on what I am talking (a tooltip) see below:
A ToolTip is a small pop-up window that appears when a user pauses the mouse pointer over an element; the Popup control provides a way to display content in a separate window that floats over the current application window relative to a designated element or screen coordinate.
Just to clear this: I know displaying extra information in tabular format, or show side by side using hidden elements or similar! They are not what I talked about nor what I am looking for! I said using tooltip to show field value!
As per pervious discussions (several times in forum or GitHub) Tiddlywiki cannot handle tooltips/popups as it should! This is a wider problem I was encountered first in Refnotes plugin! So, for now it is better to not go for tooltips/popups window or whatever it is called!
Thank you all!
Yes.
Look at Definition tiddler as I explained above
The setting is stored in $:/temp/search-in-fields/option
you can use another tiddler like $:/keepstate/search-in-fields/option or any other name not prefixed with $:/temp, $:/state to keep the configuration between session
NOTE: It seems you like to keep the options between sessions, you can use proper tiddlers as explained above to be saved when you close the current session.
@Mohammad Perfect! - Thanks a lot.
SUGGESTION: The Tool Needs Its Own Temporary Tiddler?
Ciao @Mohammad v 0.7 stiil has the issue that the temporary tiddler for the search string is shared with Advanced Search (i.e. $:/temp/advancedsearch/input). I think that is a mistake because the approach in Search in Fields uses a filtering method that is largely INcompatible with Advanced Search. It adds confusion to have, for instance, a raw regex string turn up in normal Advanced Search!
IMO it would be better that Advanced Search in Fields had its own temporary tiddler for the current search pattern???
Just a thought
TT
This is by design! If you open https://tiddlywiki.com/ and the $:/AdvancedSearch
and then Filter tab: you can see this
enter [tag[HelloThere]] and then switch to Standard or Shadows tab, what you see is in the inputbox is the same while Standard or System tab does not understand the Filter Search!
Also when you open Advanced search from Sidebar by click on magnifier, the content copied in the advanced search inputbox!
So, it is better to stick with TW method to have a similar behaviour!
Hopefully these are customizable! Search in Fields is highly modular!
searchTid to what you like!You may also keep your settings between sessions you can change other plugin wide variables here!
I think the ability to save regex patterns is very, very useful. Potentially it could help a lot in the development of specialist apps. In my own case I work with text a lot and this approach (the “2-step” method) will make it a zillion times easier to automate regular tasks editors of text need.
Best, TT
@TT
I just added few predefined regex patterns.
Please see Search in Fields Tutorial and then open Basics >Regex pattern
It shows how quickly save your own pattern and add it to the predefined pattern list!
QUERY ABOUT SHIRAZ INTEGRATION
Ciao @Mohammad, I have held back from asking this question as I don’t want to be rude.
For some uses I want Advanced Search in Fields and with the nice Tabular output sometimes.
But would I need the whole of Shiraz to get that?
Would it be possible to use only the parts of Shiraz needed?
If so, what are they?
I know this is a slightly odd question! But I think relevant if you want to use this great tool many places the full Shiraz is not so relevant to?
Just a query
TT
Hi TT,
Splitting Shiraz is possible, but maintaining is a bit difficult!
Shiraz is 126kb with Uglify it is under 100kB!
Would it be possible to use only the parts of Shiraz needed?
If so, what are they?
You need the whole dynamic tables and related CSS.
Do not forget to to have Shiraz installed on your Tiddlywiki.
https://kookma.github.io/TW-Search/#Search%20in%20Fields%20Tutorial
Your interface here reminds me of @telmiger’s “ListReveal”.
The difference is that @telmiger also allows INLINE EDIT. It is a great tool. You can seamlessly switch between View & Edit modes.
I thought you’d be interested!
Best
TT
