Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EDIT TABLE - CLONK! #3657

Open
DingBEN opened this issue Feb 2, 2020 · 0 comments
Open

EDIT TABLE - CLONK! #3657

DingBEN opened this issue Feb 2, 2020 · 0 comments

Comments

@DingBEN
Copy link

@DingBEN DingBEN commented Feb 2, 2020

Details

  • right-click table in database panel
  • pic 'Edit table' - that is OBVIOUSLY STRUCTURE
  • window comes up on data rows (Data TAB) !? !? CLONK
  • o! I have to remember to click the STRUCTURE TAB
    but if by chance the current TAB was STRUCTURE it would show that ... just like stepping on stones crossing a river and not knowing if the stone will be stable or not!
    Once I have used the app for 100s of hours and I have burnt that type flow, I would then not even expect the correct TAB to be UP, and simply know not to trust the trigger context and immediately hit the STRUCTURE TAB each and every time EVEN if it landed in that TAB, that way I save myself the CLONK! ...give this a thought, especially if you have not used the app in a while... you are returning to it !
  • bad design which has to do with the whole way this app is programmed
    one never knows when a trigger brings one to the context expected or the platter that context is in.
    and if the platter is not set to the exact context... one lands on a clonk moment and must do a retake to aim again
  • a trigger should not imply a specific context yet land in a generic one, this is a KLUGE in design.
    This is not the only place in the app where this sort of CLONK occurs!
    Indirectly or implicitly mentioned in many of my CLONK moments in other issues

Now... assuming we accept this is a bug and that a trigger that requires the STRUCTURE TAB should set the TAB... and we correct this 'decided' bug!...
what about all the other instances of the same type logic across the entire app... will we catch all of those or haphazardly keep falling in these potholes that get brought up painstakingly slowly as separate issues!? [ clean up by attrition so-to-speak! ]

Steps to reproduce - self evident

Operating system - WIN7 Pro

SQLiteStudio version - 3.2.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
You can’t perform that action at this time.