but I’m a Heinz 57.
My friend, you’re in big trouble. !
Software engineer & architect
Hehehe… I know what you mean and some “Germaness” like attention to detail has rubbed off on my. But, it’s not my heritage. I just love living here.
Then based on your last name, my guess is, you’re Northern Italian.
I was a very young boy when Apollo 11 landed on moon and I was watching it on black & white TV. Everyone was so existed. I sat near the TV and I noticed something was odd. The shadows of objects did not all match direction. Some were on one direction and some on another direction. I told my Dad and he said, it’s the Lighting. I said, but there should be ONE source of light from the sun.
Almost 50 years later rumors came out that, that landing was fake and was done in a Studio in Hollywood, based on the shadows that I caught 50 years ago.
Good tip @turigeza!
I believe the plan is to add both a site wide search to the docs and a menu search to find the menu item you are wanting faster. I’m not 100% certain on the menu item, but I’d certainly like that. It would make the docs an awesome reference.
V1 Docs are much better now than before, but there is still room for improvement.
What really helps, is “Best Practices” guideline, how components should be nested or what steps to take build proper multi layered layouts that are created properly than us doing trail & errors.
A good rich sample app can help a lot as a good resource.
If the data of the table changes, should it be assumed that the formerly selected values not be kept “alive”, if those same values are still there? In other words, if they are the same row values, why not leave them selected?
If you want to “unselect” the rows, just empty the
selectedarray, when you do the update.
However, that would seem like bad UX to me, because if I am making a decision to select rows and it takes more than 10 seconds, my selections would happen to disappear on me. That would get a WTF? out of me.
Well said Scott;