| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
|
|
|
|
| |
- minor GUI improvements
- try to fix issue 1654
|
|
|
|
| |
- added the chance to define the unmarked default operator
|
|
|
|
|
|
|
| |
- added "Search while Typing"
- added some keyboard short-cuts
- fixed some minor issues
- Filter Table is now a normal NSWindow
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
using a table approach
- not yet activated
|
|
|
|
|
|
|
|
| |
(now rolled into argumentForRow: for centralised logic), addressing Issue #791
- Update table row count at bottom of window when deleting rows in the content view
- Update localisable strings
|
|
|
|
|
|
|
| |
- simplified code
- reduced number of queries for edit status
- WHERE argument to identify first try to avoid using blob data for speed, if field is not identified with ignoring blob data then use blob data as well
|
|
|
|
|
|
|
|
|
| |
avoid the trampoline exceptions
• unified error message while cell editing
• in Custom Query table cell editing errors are displayed as tooltips and added these message if edit event comes from the keyboard
• fixed: check edit status in Content Tables only for views to avoid unnecessary queries
• used [SPCustomQuery fieldEditStatusForRow:andColumn:] consequently to simplify code
|
|
|
|
|
|
|
|
|
|
| |
active)
• view data editing
- disable add/duplicate/remove row for views
- first improvements for editing navigation via keyboard
- after editing avoid relaodTable instead use loadTableValues
- outsourced: (NSInteger)fieldEditStatusForRow:andColumn: since it will be used for keyboard editing navigation
|
|
|
|
|
|
| |
- the editing is field based as for Custom Query editing
- shouldEditRow checks if the clicked field can be identified unambiguously
- CAUTION: This must be tested heavily before releasing!! Esp. any kind of threading issues and progress spinner stuff for slower connections
|
| |
|
|
|
|
|
|
|
|
| |
- Move Table Content progress tracking onto the main thread's load timer
- Improve thread safety when autosizing
- Improve autosize to not contrain wide columns as much in tables where all columns can be shown, or if the column is double-clicked to size.
(This completes work on Issue #271 and Issue #272)
|
|
|
|
|
|
|
|
| |
- Add automatic column sizing (for columns without saved widths) as part of the value loading process
- Rework table updates to be timer based, for time-based and more regular updates. This improves speed and allows tables to update more consistently.
This results in overall smoother table loads, faster table loads, and autosizing columns. This partially implements Issues #271 and #272.
Column autosizing will likely be tweaked, and this will all also be extended to Custom Query views in a future patch.
|
|
|
|
|
|
|
|
|
| |
to restore it
• do not save tabs or a single window if connectionController is shown
• added comments
• added to SPTableContent method "tablesListWidth" to retrieve tablesList's view width
|
| |
|
|
|