At the moment, the cursor stays in a data cell, and typing may overwrite data.
Both bad orgonomics and dangerous.
Also, there is no valid reason that this button is sometimes grayed out.
Hi @ChrisNZ - I noticed the same thing when I started using this feature (the cursor position). Good news -- the development team has fixed it! It's in the next release of EG scheduled to release later this year.
Also, I think there was a defect with "output data" sometimes not enabling the Where button, but that was also addressed.
Yay! One thing fixed 🙂
I was going to start a long list of improvements post, like I did for VA, but I just dont have the time.
Also, when you run a where clause on a table, then navigate away to do something else, and come back to see the table data, the where clause is still active, but the where prompt is no longer displayed.
So there is nothing to say that the data displayed is a subset, and there is no way to know what the subset it.
So very many paper cuts...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.