diff options
author | Bibiko <bibiko@eva.mpg.de> | 2010-01-04 12:59:51 +0000 |
---|---|---|
committer | Bibiko <bibiko@eva.mpg.de> | 2010-01-04 12:59:51 +0000 |
commit | 313c5bc247548319dc1f93c9ece04ea4326d37e8 (patch) | |
tree | 3d2a0b62c92a60668dfd0020a88822ebed4a3dc2 /Interfaces/English.lproj/PrintAccessory.xib | |
parent | 25d72032f5f6296c69a5e44fb41ee9bc7942e8ca (diff) | |
download | sequelpro-313c5bc247548319dc1f93c9ece04ea4326d37e8.tar.gz sequelpro-313c5bc247548319dc1f93c9ece04ea4326d37e8.tar.bz2 sequelpro-313c5bc247548319dc1f93c9ece04ea4326d37e8.zip |
• remember scrollview port and selected row after editing in the Custom Query table view
- after reloading the entire data the table view port will be restored but this leads up to now to a "tiny jitter" (maybe fixable in the near future)
- the re-selection does NOT follow the actual edited row, e.g. if one changes a cell value whose column is used for sorting the actual edited row could appear somewhere
• if the editing in the Custom Query table view was invoked by pressing RETURN/ENTER one can go through the columns by pressing ESC but up to now that editing will be interrupted after the user pressed OK
- this behaviour is temporary and should be fixed in the near future by storing the new row data temporarily; after editing the last column AND if all columns have the same table origin the row data will be updated. To allow the row editing for columns which have different table origins could probably cause inconsistencies.
- further discussion is needed
Diffstat (limited to 'Interfaces/English.lproj/PrintAccessory.xib')
0 files changed, 0 insertions, 0 deletions