Fixed: underscores missing when accessing CPColor's components ivar

[daboe01]

previously, the ivar was erroneously accessed by the property name using dot syntax.
this is corrected by adding the underscore appropriately.
credits: https://groups.google.com/forum/?fromgroups#!topic/objectivej/DbHN1ffcjO0

[cappbot]

Milestone: Someday. Label: #new. What's next? A reviewer should examine this issue.

[aparajita]

Danke. You tested it?

[daboe01]

no.

maybe michael can test it in his app?

@michael:
you can download the fixed capp framework here:
https://github.com/daboe01/cappuccino/tree/fix-CGContextDrawRadialGradient

best greetings,
daniel

Am 07.09.2015 um 05:16 schrieb Aparajita Fishman notifications@github.com:

Danke. You tested it?

—
Reply to this email directly or view it on GitHub.

[cappbot]

Milestone: 0.9.9. Labels: #ready-to-commit, AppKit, bug. What's next? The changes for this issue are ready to be committed by a member of the core team.

[Dogild]

More informations here : https://groups.google.com/forum/?fromgroups=#!topic/objectivej/DbHN1ffcjO0

The manual test CPGradientTest looks good with the current version ! This fix will work when using CPColor's array instead of using the method CGGradientCreateWithColorComponents() (which is how cocoa works)

[cappbot]

Milestone: 0.9.9. Labels: #needs-confirmation, AppKit, bug. What's next? This issue needs a volunteer to independently reproduce the issue.

[cappbot]

Assignee: Dogild. Milestone: 0.9.9. Labels: #needs-confirmation, AppKit, bug. What's next? This issue needs a volunteer to independently reproduce the issue.

[Dogild]

According to the Cocoa doc (https://developer.apple.com/library/mac/documentation/GraphicsImaging/Reference/CGGradient/#//apple_ref/c/func/CGGradientCreateWithColors), when using the gradient color you need to pass CGColor and not CPColor.

Everything looks good in the framework right now (manual test in CPGradientTest)

[cappbot]

Assignee: Dogild. Milestone: 0.9.9. Labels: #needs-confirmation, #works-for-me, AppKit, bug. What's next? Attempts to reproduce the problem described by this issue have failed to reveal any erroneous situation.