Now, why they don't all have "Evernote" checked is confusing to me. They were all entered in the Evernote grid so they should have it checked automatically when the item is created. Actually, I'm noticing that all the top level items have "Evernote" checked and the lower level items do not.
Now about the 80-something items that keep disappearing. All except one do NOT have "Evernote" checked. All these items were created in the Evernote grid. I would have expected the default behavior is to have the grid name field checked when items are created in that grid.
Again, remember, I don't ever touch the source box or do anything with filters.
that is default behaviour - this way you get to see the parent items & can expand as you wishThat is not surprising as Armando and I think alike on a lot of this stuff. So, I don't see what's the point of having a show all subitems feature because there's already that little expand tick under the item bullet that hides/expands the subitems. If I don't see the tick there, I assume there are no subitems.
I know Armando works differently but I can never keep up with him
It's confusing to me. I understand if you want to hide items using the filters and stuff. That makes sense, it's logical. But this is confusing because the item is being hidden because it's a sub-item? That's confusing to me. When an item is created, I prefer the grid it's created in to be automatically checked. It doesn't make sense to add an item to a database and then the item is not associated with any grid by default. By default, all items should be associated with the grid it was created in. If you don't like that behavior, then you can uncheck it later. That makes more sense to me.
This is an interesting discussion... I'm running short on time but....
Yes, this is the default behavior.
I talked about this matter with Pierre quite a few times as I find this behavior unintuitive -- flat view should show all items, even when subitems are not meeting the source. Because flat view doesn't show all items with the default settings (inheritance is off), i have to enable inheritance for all fields that are used as grids sources.
And so I think it would be better for "inheritance" to be the default setting for grid sources (at least the simple sources).
one of course has to keep in mind that these "default behaviors" will have some consequences and so they have to be well thought of before they're implemented.
There were reasons for Pierre's initial choice... mainly influenced by Ecco's logic, IIRC; the problem is that SQLNotes is much more sophisticated, allows multiple parents, etc. so... Ecco's way is probably not the best. Pierre can comment on that if he wishes to.
So, like I said, I personally tend to enable inheritance for all fields which are used as grids sources -- with a few exception. The reasons are simple, I want to : 1- be able to see all items when Hierarchical view is off, 2- be able to filter in/out items from a grid more easily, 3- be able to trace more easily all the items contexts (grids) in which they're used (especially when they're used in different grids...), 4- be able to use the "quick add item" to send bits of data to my database, assigning different fields without destroying the logic in a grid (ie : all items in a grid ave the main Yes/NO field-source "ticked", not just a few here and there).
As for the "full hierarchy" mode, etc. I never ever use the normal (not full) hierarchy mode. I don't because items won't appear more than once (when they have multiple parents) in the hierarchy, and I have no use for such a function. I wonder if anybody does? In the end, I always use either the Full hierarchy mode, or "flat" mode.