This is a typical job name:
show_tasktype_name_v### ,
spe_anim_horse_v343.max
It DL5 we could type parts of the name in the search box ie “spe horse” and it would find it
In DL6 we can’t do that any more unfortunately.
Could this be changed to be in line with DL5 again please?
Thanks!
Patrick
Hey Patrick,
The search field supports regular expressions, so you can use this:
Cheers,
Ryan
Hey Ryan,
that is for sure great and I wasn’t aware of that.
I do think it will be too complicated for most people especially since it used to work just easily.
The default search will be just parts of a name separated by space (same as on google etc.)
So how about you translate " " to “.*” implicitly.
Then we got the best of both worlds. It works like it used and we got the power of regular expressions when we need it.
Best,
Patrick
An issue with that though is what if you need the space because there are spaces in the job names you are searching for? I’m sure after a couple of iterations, it should be easy enough to re-train the brain to remember “.*” instead of " ". 
I know regex so I’m not worried. But there are many users out there who will just be annoyed that it doesn’t work anymore.
Regarding searching for a space. You could just do what google and all other search engines do. You use quotes if you want the text to be literal:
“spe horse” means “spe[space]horse”
spe horse means spe.*horse and searches for anything that starts with spe and ends with horse
On the other hand there might be more pressing issues. So take your pick.
This is just my vote
Yeah, I hear you, and you bring up a good point about how other search engines handle it. Back in v5, we were manually handling how the search filtering works, whereas in v6, we just pass the string to Qt and it automatically filters it for us. It’s definitely possible to write custom filtering for Qt though, so that’s likely what we’ll have to do to support this. Not sure at this time where it would fit on the roadmap, but if I had to make a guess, probably not until 7.0 goes out.
Cheers,
Ryan
Ok sounds good.
Thanks
I’ve always appreciated quicksearches which converted “Bob Jones” -> “BobJones". Our internal pipeline tools had an auto conversion behind the scenes where it would do a string substitution for " " -> "” before passing it to the filter.
After thinking about this some more, I wonder if we should just replace " " with “.*” under the hood…
Yes it would be easy and it would bring it back to what it used to be.
Then if somebody complains that they can’t search for spaces you can just add the quote option from above.
Sounds like a good plan