Does anyone have any practical experience with "suite" preferences? I'm finding
the API lacking so much that it's almost useless, but I'm willing to give it
the benefit of the doubt.
I've come across this a few times now where I want two applications to share
some common preferences. In my cur
I don’t know of an easy workaround. Back in the day I would have suggested
creating a category on CGColor that adds the required archiving methods,
but doing this will get you rejected from the App Store. You may need to
write a function that walks through a mutable attributed string and finds
all
On Feb 26, 2012, at 9:44 PM, Michael Swan wrote:
> the thing that doesn't make any sense is that if NSAttributedString conforms
> to the NSCoding protocol it must be able to fully pack itself up when
> encodeWithCoder: is called on it which means that it should already be taking
> care of enco
I have a UIDocument with a single property, an NSAttributedString, that I am
trying to save. The documentation says that NSAttributedString conforms to the
NSCoding protocol so I'm using NSData *docData = [NSKeyedArchiver
archivedDataWithRootObject:self.contents]; where self.contents is the
NSA
On Feb 26, 2012, at 7:00 PM, Graham Cox wrote:
> This one is embeddable and has a BSD license:
> http://ridiculousfish.com/hexfiend/
+1. Hex Fiend is a great app, and an embeddable view of it would be great.
—Jens
___
Cocoa-dev mailing list (Cocoa-d
On Feb 26, 2012, at 7:38 PM, Graham Cox wrote:
>
> On 27/02/2012, at 1:27 PM, Karl Goiser wrote:
>
>> use double parentheses
>
>
> Yes, but that's not what the poster was suggesting. I pointed out why that
> form is bad.
>
> This is a solution, but so is Apple's recommended form.
>
> --Grah
>
>>>
>> Doesn't necessarily work quite that simply with Unicode and NSString and its
>> family.
>> From a file that is ASCII data you could create a C array like that ...
>
> Huh? William didn’t say anything about where the data came from. As long as
> it’s already in a C byte array (or a
On 27/02/2012, at 1:28 PM, Graham Cox wrote:
> Search for a 3rd party solution. There's one out there that's free and works
> well, but I forget its name.
>
This one is embeddable and has a BSD license:
http://ridiculousfish.com/hexfiend/
--Graham
__
On Feb 26, 2012, at 6:20 PM, John Joyce wrote:
>>
> Doesn't necessarily work quite that simply with Unicode and NSString and its
> family.
> From a file that is ASCII data you could create a C array like that ...
Huh? William didn’t say anything about where the data came from. As long as
it’
On Feb 26, 2012, at 5:28 PM, William Squires wrote:
> It's easy enough on an NSTextField (whether it's set up as a static label,
> or as a data-entry-type field), but where's the .text property of an
> NSTextArea?
NSTextView? The .textStorage property is an instance of NSTextStorage, a
subcl
On 27/02/2012, at 1:27 PM, Karl Goiser wrote:
> use double parentheses
Yes, but that's not what the poster was suggesting. I pointed out why that form
is bad.
This is a solution, but so is Apple's recommended form.
--Graham
___
Cocoa-dev mailing
I think you can turn it off, but I think you can also use double-()'s to
suppress it:
if ((self = [super init]))
On Feb 26, 2012, at 5:40 PM, Graham Cox wrote:
>
> On 27/02/2012, at 12:13 PM, William Squires wrote:
>
>> I prefer the "if (self = [super init])" combined form, myself.
>
>
> On
On 27/02/2012, at 12:28 PM, William Squires wrote:
> It's easy enough on an NSTextField (whether it's set up as a static label,
> or as a data-entry-type field), but where's the .text property of an
> NSTextArea?
Do you mean NSTextView? use its -string method.
> Also, what would be the easi
If you use double parentheses, you won’t get the warning:
if ((self = [super init])) {
}
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-a
> It's easy enough on an NSTextField (whether it's set up as a static label,
> or as a data-entry-type field), but where's the .text property of an
> NSTextArea?
> Also, what would be the easiest way to implement a view that showed a memory
> dump? i.e.
The easiest way is to find out what you
Actually, I believe there's a specific build setting that special cases just
this construct; it seems to default to 'on' at least in Xcode 4.2 under SL, as
I never get the 'unintended assignment' warning, even though it does warn me in
other cases where I might type "if (a = b)" or some such.
On 27/02/2012, at 12:13 PM, William Squires wrote:
> I prefer the "if (self = [super init])" combined form, myself.
One potentially annoying thing about this form is that, if you compile with
plenty of warnings on, such as the possible unintended assignment warning (if
not, why not?) then thi
It's easy enough on an NSTextField (whether it's set up as a static label, or
as a data-entry-type field), but where's the .text property of an NSTextArea?
Also, what would be the easiest way to implement a view that showed a memory
dump? i.e.
:hh hh hh hh hh hh hh hh <- ASCI
>
>
>> I'm just saying the stepper itself should not have a value, it should send
>> actions to a controller so it can manipulate a numeric value in a model
>> object, or it should be able (using bindings) to increment/decrement a
>> model's value. Using the UI as a model isn't what MVC is al
I'm rewriting an existing Carbon application with Cocoa, and am working
on the preferences. One preference that the user should be able to set
is a default font and size for text display. In the Carbon app, there is
a pop-up button with a font menu, and a combo box for the size. This
doesn't se
This is one of those things that comes from the C background - any non-zero
value is true; thus the two statements are equivalent. I prefer the "if (self =
[super init])" combined form, myself.
On Feb 24, 2012, at 8:50 AM, Oleg Krupnov wrote:
> An interesting question. The following samples a
On Feb 26, 2012, at 4:44 PM, William Squires wrote:
>>> Why didn't they just make the NSStepper a custom view that draws two
>>> arrows, and has two sent actions that you can connect? Or even a variation
>>> of NSMatrix with two button cells that look like arrows. That would avoid
>>> the probl
On Feb 24, 2012, at 5:53 AM, Joshua Tidsbury wrote:
> On 2012-02-23, at 9:44 PM, William Squires wrote:
>
>> Ever since the first release of iOS (then called iPhone OS), the UISwitch
>> has really bothered me:
>>
>> 1) It takes up too much valuable screen real-estate compared with a checkbox
>
On 27/02/2012, at 11:44 AM, William Squires wrote:
> I'm just saying the stepper itself should not have a value, it should send
> actions to a controller so it can manipulate a numeric value in a model
> object, or it should be able (using bindings) to increment/decrement a
> model's value. Us
On Feb 23, 2012, at 2:13 PM, Seth Willits wrote:
> On Feb 23, 2012, at 6:16 AM, William Squires wrote:
>
>> From what I've read, the NSStepper has a bug (though practically, you'll
>> never see it); if one were to click the up or down arrow on the control 2^32
>> times (assuming it's value is
According to http://nslog.de/posts/147 go to iTunes Connect > Manage Your Apps
> Download Application Loader (in the footer). Find Application Loader 2.5.1
at: https://itunesconnect.apple.com/apploader/ApplicationLoader_2.5.1.dmg
On Feb 27, 2012, at 3:02 AM, Dave Fernandes wrote:
> Where does
Where does one get this Application Loader? I have a similar crash just trying
to export the application.
On 2012-02-26, at 6:44 AM, Evadne Wu wrote:
> If you are running 10.7.3 then get the new Application Loader. It
> works. The OS X update broke (!) app validation.
>
> On Feb 26, 2012, at
On 23, Feb, 2012, at 09:50 AM, H. Miersch wrote:
>
> On 21. Feb 2012, at 8:13, Martin Hewitson wrote:
>
>> Dear list,
>>
>> If an app uses iCloud to sync data between machines, should we provide the
>> user a check-box to opt-out of iCloud syncing? Is there are recommended best
>> practice h
If you are running 10.7.3 then get the new Application Loader. It
works. The OS X update broke (!) app validation.
On Feb 26, 2012, at 19:14, Georg Seifert wrote:
> Hi,
>
> I’m using xCode 4.3. If I try to validate my app prior to uploading it to the
> Mac App Store, it constantly crashes.
>
Hi,
I’m using xCode 4.3. If I try to validate my app prior to uploading it to the
Mac App Store, it constantly crashes.
I get a crash report that says:
UNCAUGHT EXCEPTION (NSInvalidArgumentException): -[DVTFilePath compare:]:
unrecognized selector sent to instance 0x409ab29c0
The same happen
30 matches
Mail list logo
