This patch contains the following:
- FSEvent is now at files level instead of folders level. This allows to drop the registry in plist and improve the performances
- When you remove a J file, the mirrored H file is removed too
- .xcodecapp-ignore has been added to the FSEvent stream. ignored token are updated in live
- By default XCC ignores all .git, .svn, .hg .xCodeSupport, Frameworks and Build folders
- When you quit XCC without stop listening of the project, at next launch it will resume on the same project
- Help has been added
- Help is displayed at first user launch
- The Error & Warning table doesn't pop ups automatically, instead it displays Growl (you can then open the panel for more informations)
- The code has been refactored into several classes, one for UI thing, another one for XCC worker
- Several bugs has been fixed
- The about window now displays the version number
- The main window has been removed
- Several other small enhancements.
This is XCC 2.0.
If there is no vertical scroller, or there is no horizontal scroller, due to autohiding or scroll view settings, a single visible overlay scroller should extend all the way to the edge of its dimension.
---
Cocoa compliance.
* updated manual test: log a text only when user clicks a radio button butnot when using the CPButton that uses setState:
* ignore .xCodeSupport folders.
---
- Enhanced -description method of CPImage and CPColor to show the exact content, especially for pattern colors.
- Added CPColorWithImages() convenience function, analogous to PatternColor() function used in theme descriptors.
- Added @cond/@endcond in CPColor to ignore local variables.
- Sample app included. See the console for samples of -description output for all color/image types.
In the PlatformWindows test, change the window title both when theWindow is a non platform window and when it is a platform window to verify that the browser window title changes only when it should.
Everything in the README has been fixed except 3 and 4. 4 is outside of the issue scope and 3 works as intended (nearly). The array controller does not have `setAvoidsEmptySelection:NO` so an empty selection should not be possible unless there are no items.
---
I discovered the following behavior that is not in conformance with Cocoa:
- Backspace, tab, escape, and space are considered key equivalents.
- Function keys (F1 - FNN) are not considered key equivalents.
- CPTextField executes `performKeyEquivalent` twice if a field is first responder.
Build this Cocoa project and debug it: http://d.pr/Xc3h
Take a look at the debug log while typing some keys. You will see that backspace, tab, escape and space do not trigger `performKeyEquivalent`, and that `performKeyEquivalent` is only executed once for the first responder.
Then run the performKeyEquivalentsTest app in this commit and look at the console log while trying keys in the text fields. If you turn the old code on, you will see how `performKeyEquivalent` is executed twice for the first responder.
For reference on key handling code, I consulted this:
http://developer.apple.com/library/mac/#documentation/Cocoa/Conceptual/EventOverview/EventArchitecture/EventArchitecture.html%23//apple_ref/doc/uid/10000060i-CH3-SW11
---
Adds -scrollViewWillScroll: and -scrollviewDidScroll: delegate methods to CPScrollView.
These methods are not in AppKit but exist in UIKit. Useful for lazy loading data in a view, for example a CPTableview.
Tested in the CPScrollView example.
Conflicts:
AppKit/CPScrollView.j
Antoine Mercadal
Aparajita Fishman
Sjoerd van Geffen
Alexander Ljungberg
Stephen Ierodiaconou
Klaas Pieter Annema
Randy Luecke