| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
modify a cell
• in Custom Query table after field editor sheet dismissing preserve the the edited field selection
|
| |
|
|
| |
the actual edited line due to new data will come up in another line
|
| |
|
|
|
|
|
|
| |
data in Content tables
- now each cell can be selected via keyboard navigation regardless whether it's editable or not; only if the user tries to modify it then it will be checked if it's editable or not - for speed while navigation
- fixed issue for view data editing to show blobs in editor sheet if user wants to modify it
- Note: still work on progress
|
| |
|
|
|
|
|
|
|
|
| |
since we need that for Content and Custom Query table; only class specific stuff like ESC trapping will handled in the actual class
• enabled in cell editing for Custom Query tables
- also added spreadsheet button to Custom Query status bar
• fixed ESC trapping: F5 can be used for completion
• simplified [SPCopyTable keyDown:] for trapping ENTER/RETURN key
• some code cosmetics
|
| |
|
|
|
| |
- removed unnecessary header indicator image setting
- set [[customQueryView onMainThread] setNeedsDisplay:YES] to ensure to display table rendering correctly after changing the sort order
|
| |
|
|
| |
Custom Query table
|
| |
|
|
|
|
|
| |
- by clicking a the same table header the sort will changed to desc, asc, no sort order, desc, asc, etc.
• fixed sorting issue for Custom Query table
- reset sort order status before executing a new custom query
• code cosmetics: reduced file size for SPCustomQuery.m
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
[aString appendString:[NSString stringWithFormat:]] by
[aString appendFormat:]
since it's much more faster
• first look at loop where several [aStr appendString:] occur to try to combine them into one appendString or appendFormat since the allocation of memory takes really time
Note: I tested all my changes but we should test it further to be sure that I didn't a mistake!
|
| |
|
|
|
|
| |
display an alert sheet which waits for the change in the didEndSelector method of a passed class NSInteger variable
• applied the SPBeginWaitingAlertSheet routine to Pref > Editor's check for unsaved color themes and in SPCustomQuery's sheet about Stop/Continue/Run All if a query failed after executing "Run All"
|
| | |
|
| |
|
|
|
|
|
|
| |
- 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)
|
| | |
|
| |
|
|
|
|
|
|
| |
syntax to \n. This addresses Issue #652.
- Clean up SPSQLParser, and use a few more CFString methods to avoid obj-c messaging in loops
- When importing SQL using autodetect, perform a manual SET NAMES if possible to cope with poorly-exported files.
|
| |
|
|
|
|
|
|
| |
strings
- Tweak MySQL help search to include a localisable language code for results in requested languages
This addresses Issue #743
|
| |
|
|
|
|
|
|
|
| |
- Exporting BIT fields properly in SQL dumps using b'x' notation.
- Properly handling editing of BIT fields in both the content and custom query results views.
- Correctly display BIT fields in the content view, where binary values are zero-padded to the specified length of the field.
(Note, that the new BIT handling logic has only been added to MCPKit's MCPStreamingResult and MCPResult as the latter does not keep a record of the field's length which the new functionality depends on. Needs to be discussed).
|
| |
|
|
|
|
|
| |
collapse via code which was originally causing the problem. Also apply the same fix to SPCustomQuery.m.
(Note that this also identifies a probable cause of views going slightly out-of-view if views are collapsed and expanded a lot - the autoResizesSubviews property is disabled and re-enabled in BWToolKit surrounding a collapse, but this is done using a timer with the exact time interval as the corresponding collapse/expand frame resize. This sets up a race condition, where if the timer fires before the animation completes, the internal view will be slightly clipped. May require a BWToolKit fix)
|
| |
|
