Real Basic, Questions on layer filters

Rhino Rhino for Windows
1

For I love asking real basic stupidish questions that really aren’t all that stupid, but stupid in that all everyone else on the planet is beyond genoius, which I have left misspelled so that someone reading this question can at least comment on my inability to spell genius, thus boosting their self-esteem and increasing the odds of getting a answer from someone whom probably really does in fact know, mostly all.

So, rookie here in investigation of layer filters which have a use, but not so much too a little tike such as myself at the currenty moment. This is because grouping, selecting by, recoloring objects/by layer, changeobjectcolor toolbar, are still on the list to actually know off hand. Basically knowing where the button is in a split second. Theres lots of tools and possibilities to organize and select parts of objects, etc…

So, I’ve been playing with the filter for a couple hours.

I cannot figure out how to do the following

List of layers
-Layer 1
-Banana

  • Banana 34
    -Layer 4
  • Banana 39

What I would like

  1. To figure out how to filter and get hits for all layers with banana as a part of their name.

It seems that no matter what I do, I cannot get Banana 34, and Banana 39 to come up in the results.

It doesn’t make sense to name your layers the exact same name so that they show up in a filter, is it even possible to have layers with the exact same name?

So what am I doing wrong here?

How do you get queries to have to match more than character, such as just Ban, and disregard the rest of the name. Only searching for any match in the name?

Or a search for a number and get results from layers with letters and numbers?

I know this should be possible. It’s very possible that someones working on script to place a “Click Here MonkeyBoy” with the intention of hacking me, installing it in my toolbar manager, and when I click on it, a gorilla’s gonna pop through screen and pinch my nose. It’ll probably only take them 10 minutes, and they’ll have already taken out 3 loans and converted to bitcoins.

1 Like
2

Use an asterisk * (“wildcard”)
As in:

banana* (gets all names that start with banana…)
*banana (gets all names that end with …banana)
*banana* (gets all names that contain …banana…)

This is also pretty much Windows standard for searches…

–Mitch

1 Like
3

Awesome! I just didn’t think of that, the hour I thought I had tried it all. Thanks a lot. Ya, it kinda being universal is good to know too. Maybe for some database’s too? You live, you learn. Heck, 1.5 years ago I dint know about ctrl c and ctrl v being universal! Now I’m getting myself a razor anasi keyboard, and razor naga mouse for all my hotkey action! So, with ditto, hotkey hardware, etc…I’m making progress. Thank you.

4

(Without saying, correct me if I’m wrong)

(NOTE, ASTERICKS ARE NOT SHOWING IN THE BROWSER, A PERIOD IS BEING USED AS A SUBSTITUTE FOR A ASTERICK)

Okay, so I completely understand using the asterick*, and the question mark?, and combinations of them.

What I do not understand is the # and the alpha.

It seems that they should either operate as add ons to queries containing asterick, or on their own in a query.

Problems with Logic

  1. 7#, according to microsoft’s query logic should yield anything starting with 7, and having two total characters.
    This is their example.

  2. The same should go for the alpha. a&a query should yield, starts with a, ends with a, is exactly 3 characters in total length.

  3. *a&a query should yield any record(layer name) that ends with the sequence (a (single replacement wildcard alpha) a and is at least 3 characters in length.

  4. 12#7 should yield any record(layer name) that contains the sequence 12, single number replacement wildcard, then 7, in that 4 character sequence anywhere in a record(layer name) whether in beginning, end, and whether having characters in addition to that sequence.

  5. 7#1 should yield 1 of 10 possibilities, if they are present as entire layer names, 3 digits.
    Must start with 7, and end in 1.
    Possibilities: 701, 711,721,731,741,751,761,771,781,791

5
  1. (Astericks are not showing in browser I will do a period instead) .7.#1 should yield layers containing 7, having 2 uninterrupted digits at the furthermost right end of the name with the last being 1, variable amount of total characters, and the wildcard replacement digit cannot be 7, unless the 7 is in addition to the 7 found in the beginning of the query (asterick contained 7). This would mean that the answer cannot be 71, and although a total digit allowed in query is not limited, it does therefore have a minimum. I figured out this is because when the query searches for both parts of the function, it may find the first part of the function, but the second part has to also be true. When the first part catches the 7, in the example, it cannot be used to validate the rest of the query. It is like grabbing the 7 from a shelf, looking to grab a 1 and whatever is next to it. But since the 7 is in the hands not in shelf, it wouldn’t find it.

The other reason it cannot complete with 71, it does have a minimum character amount of 3. 7 counts as one character, wildcard # counts as another, and then 1. That is 3. Asterick’s do not count as a character in any totals applicable to the user.

Moving on to the next example.

  1. Lets say your names are:
    10
    11
    12
    13
    14
    15
    16
    17
    18
    19
    20

The query (Astericks are not showing in browser I will do a period instead) .1.# does not work. 2 character MIN, must contain 1 anywhere, must end in a #, and that ending number can be any number. This doesn’t work in Rhino.

Switch that to a question mark, and it works

(Astericks are not showing in browser I will do a period instead) .1.? 2 character min, must contain 1 anywhere in name, must end in a character(letter or number), and the ending character can be any character except the first character in the records name because of the deduncy type rule.

Testing Theory
1*1 This is 1.1

a1 This is .a.1

aa This is .a.a

Theory of astericks only disappearing in all number sequences is gone, as with letter on sequence being fine is gone.
Anywho, problems with # and & wildcards, and this thread!

6

Here is some stuff I put together on using the rhino filters, although the # and alpha wildcards I cannot figure out for now, after a half day of testing.

Anyways, it seems many different query formats are used across different developer platforms, and applications.

The ones these maps are in reference to should be true for most if not all of them. Some have periods instead of astericks, and such. But the format and rules of the atserick should all pretty much be the same. Same for question mark. They are also likely the most common to a average user of any of the various software. Even using these 2 basic features on say a search engine would put you in a different category than of the average searcher.

With that being said, they will likely be the easiest, and fastest to use if you stick to a particular way of organizing layers for uniformity and production. With layers logs, you can log your actual queries for particular things, along with organizing your objects, settings, layer settings etc…To help you from making mistakes, and overall promote excellent file management skills which leader to a happier and more productive work environment.

Anywho, there will be more to come regarding the rules of wildcard mindmaps, application. The info I have, the formatting takes challenging to figure out how to teach myself, in as many ways I can, with the most easily readable, cross-reference style all inclusive mindmaps that fit on 1 screen or sheet of paper to print legibly.

So, here are a couple of resources I used, and I left out the ones that didn’t provide much useful insight.

But, it took a lot of rereading to understand and apply all the rules, and to become proficient.

The form could help you become proficient. The form mindmap, and the asterick main mindmap are not including all of the updated and modified rules. I’m in the works in organizing it into the best format. Although, with resources, and a little problem solving, you should be able to figure out my terms easier than I did. But I will likely post the additional rules, examples and application since I will need it for myself anyways. Kinda like remixing your quizzes, rewriting the questins you don’t remember, which usually involves breaking it down into 3 more questions, with some new fresh stimuli.
ANyways, Links

This ones good

Microsoft Developer Format

Asterick Main Rules, that could get you by if you wanted to do it the easy way only.

Then a form, that can help isolate the musts , and the variables in a given query. Although modified version with better rule associations is comin. As well as a all rules map, and as I go, possibly some sample Layer Management logs, with different systems pros/cons, (which will have columns to log various queries perhaps). I’ll do this, and to study workflows, visability, selection, settings to figure out exactly which layer naming system might work the best for me.

7

Here’s my Filter Rules thus far for Rhino Filter Searches only. I still cannot get any queries using a # or & wildcard. But these all apply to rhino for the asterick and question mark. I have expanded on terms from other resources, mixed and matched, and created rules based on my findings. I’ve edited as many of the statements to be true as I can. But, funny thing about logic, which I have figured out on my own years ago. Any statement can through the use of vocabulary, syntax, and explaining your logic can be turned true or false through arguments, and grammar/vocabulary/syntax loopholes. Third Alternative-like loopholes.

So, feel free to correct me on a false statements. I just wanna learn everything the best I can. Maybe help a few others with some cheat-sheets.

8

there is no shame to be stupid in way of questioning every thing