sts.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/graham%
40ictinternational.com.au
This email sent to [EMAIL PROTECTED]
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not pos
In a UI I'm working on, I have an occasional need to use the Font
Panel from a floating panel (the panel has a "Font..." button that
brings up the Font Panel to change the font attribute of something in
my panel).
The problem is that the Font panel sends its changes to the
changeFont: met
I have an object embodying a data model. In a document-based app,
there would be one of these per doc. There can be one or more views
on this data (for example a split view of it). Currently I don't have
a controller between the two - the view is pretty specific so it
implements the control
hence retain it.
I do need to support 10.4, so I'm not using G/C. However I'm
comfortable with the retain/release mechanism in general.
----
S.O.S.
On 05/03/2008, at 4:05 AM, Jens Alfke wrote:
On 3 Mar '08, at 6:16 PM, Graham wrote:
The question is: would the better
Thanks for that...
I thought this seemed a bit too obvious to have overlooked and sure
enough, it's new for 10.5. I should have mentioned I need a solution
for 10.4 or later. Any ideas?
S.O.S.
On 05/03/2008, at 3:17 AM, Benjamin Stiglitz wrote:
Is there a way to hook up the Fo
On 25/02/2008, at 8:53 AM, Development wrote:
I'm sure this is a simple problem
Actually, it's not.
Creating interactive drawing successfully has many pitfalls.
One avenue you might consider is using an already written library.
I'm working on one written in Cocoa called DrawKit: http://
r comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/graham%
40ictinternational.com.au
This email sent to [EMAIL PROTECTED]
___
requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/graham%
40ictinternational.com.au
This email sent to [EMAIL PROTECTED]
___
[NSString floatValue] won't evaluate expressions, only convert string
representations of numbers.
I have written a category on NSString that does evaluate expressions
however; you can find it here: http://apptree.net/parser.htm
HTH,
S.O.S.
On 27/02/2008, at 4:55 AM, C Sandeep w
ists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/graham%
40ictinternational.com.au
This email sent to [EMAIL PROTECTED]
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not po
good, because of
course it always does respond to the selector in the base class, and the
framework has no knowledge of subclasses beyond its own borders. Seems like I’d
need to drop down into the runtime functions but it’s still not really obvious
what would work. How do Apple do this?
—Graham
of things. But on the client side, implementing
these objects as delegates would always have been a lot more effort than
subclassing. I don’t see that the effort is worthwhile just to avoid the
possibility in the future that one of the override points turns out to need
more parameters.
—Graham
P
akes
place or not, so sorry I oversimplified by leaving it out of the story.
—Graham
___
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
purpose to having that property
‘copy’, it can be ‘retain’ (or ‘strong’) and it will save you a small amount of
space per instance.
These are minor nits to be sure, but often it’s this that makes the difference
between a good class and a great one.
—Graham
> On 8 Sep 2015, at 3:34 am, D
positions in varying styles. Using tricks as described it scrolls
smoothly.
—Graham
> On 28 Sep 2015, at 3:42 am, Ben wrote:
>
> Hi list,
>
> I'm needing to draw somewhere in the order of 1,000,000 different strings in
> a scrollable grid view and am struggling to ge
hat task.
These days a scroll view is layer backed by a tiling layer by default, so using
CATextLayers in this way should give you about as fast a drawing system as is
currently possible.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
ng up the heights of all possible rows
above the line, you’re probably doing far too much work - the table already
knows which views are visible and where they are, so there should only be a few
to consider at most.
—Graham
___
Cocoa-dev
> On 1 Oct 2015, at 5:04 pm, Peter Hudson wrote:
>
> Legacy code I’m afraid Graham - written some years ago.
> I simply want it to look better for now while we're getting on with the
> re-write.
> The new version indeed uses view-based table views - and works a lot
hat’s the correct solution unless more info is provided.
—Graham
___
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-admins(at)lists.apple.com
He
ght
well believe it is, as you’ve silently changed its apparent type. I’d call that
a bug. If it’s not a bug, and your cleint code is happy, then there’s no reason
to redeclare ‘stuff’ as a different type at all.
—Graham
___
Cocoa-dev mailing list (
explanation as to why Swift doesn’t suck doesn’t fit
any notion in compuer science that I have ever heard of in almost 40 years of
programming. Maybe it’s just the jargon that needs a clearer explantion (I
suspect it is), but when things are as clear as mud as this, you are not going
to see th
good a value as any - just a pity that’s a valid
address in many (most?) cases. Optionals may solve that more elegantly, but I
bet they would have been way to much overhead in a 1970s system - even
compilers were pretty half-baked at that time.
Anyway, thanks
point me at what I should be doing.
—Graham
___
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-admins(at)lists.apple.com
Help/Unsubscribe
> On 8 Oct 2015, at 11:50 am, Graham Cox wrote:
>
> I understand that cells are going away, but there currently doesn’t seem to
> be a replacement for returning a custom field editor for a given text field
> that doesn’t involve its cell. If there is, and I’ve missed it, tha
over method on NSControl, I
wouldn’t have to do that. As cells go away, a cover method is going to be
needed to maintain the same functionality, it just doesn’t seem to exist yet
(or is private).
Radar time.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@
ADIANS_TO_DEGREES( r ) ((r) *
57.29577951308232)
—Graham
___
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-admins(at)lists.apple.com
Help/U
> On 10 Oct 2015, at 3:21 pm, Rick Mann wrote:
>
> The compiler should figure that out either way it's written.
Does it actually replace a function call with an inline constant multiply?
—Graham
___
Cocoa-dev mailing l
> On 10 Oct 2015, at 3:54 pm, Jens Alfke wrote:
>
> There’s very little reason to use macros for things like this, when an inline
> function is as efficient and safer.
>
Probably another example of modern technology passing me by - used these macros
for >20 years… ;)
Here’s a quick test I
operation is
undefined? Surely a preincrement is defined to happen first, that’s why it’s
called a PREincrement? Or does the warning refer to something else? I’ve used
this form of expression for years without any issues, why is it suddenly one?
—Graham
> On 14 Oct 2015, at 9:02 am, Raglan T. Tiger wrote:
>
> NSFont *sysFont = [NSFont systemFontOfSize:10];
> NSString *sysFontName = [sysFont fontName];
> CGContextSelectFont(ctx, [sysFontName
> cStringUsingEncoding:NSASCIIStringEncoding], 90, kCGEncoding
od stems from years-old habits
of writing embedded software, where ++ would typically compile to a single
instruction on the 8051 or similar where every clock cycle counted (and
=+1 would not). I guess these days it’s a moot point :)
—Graham
___
, only now does Xcode 7 complain, presumably
because only now is the _Nonnull attribute added. But either the documentation
or the addition of _Nonnull is wrong.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
window.contentView addSubview:self.vc.view];
—Graham
___
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-admins(at)lists.apple.com
Help/
ork and means going
through old code that’s working fine, with the possiblity of creating bugs.
Has this approach always been bad, or is it a new thing? I’m all for tightening
up sloppy coding, but could it be that in this case the non-null qualifier is
in error?
—Gra
> On 28 Oct 2015, at 10:24 AM, Graham Cox wrote:
>
> due to the addition of the NON_NULL qualifier
Actually, I should amend that: it doesn’t have ANY qualifier, so that appears
by default to mean that it’s NOT nullable. I’m still getting used to this
additional sy
> On 28 Oct 2015, at 10:53 AM, Alex Kac wrote:
>
> Have you tried simply passing in a blank dictionary? Is that OK?
Yes, that works OK. It’s at least a simple way to shut the warning up, though
strikes me as unnecessary and inefficient, FWIW.
—G.
__
ion
to populate a list of errors and what the user can do about them. If the user
can’t do anything about them, then there’s probably no point going into even
that much detail.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please
using the classic
struts to each side and a spring in the middle.
—Graham
___
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-admins(at
Thanks Ken, that works fine. Eyebrows a little bit raised that this is needed,
but then segmented controls are horrible to deal with in any case.
—Graham
> On 10 Nov 2015, at 3:35 PM, Ken Thomases wrote:
>
> On Nov 9, 2015, at 9:36 PM, Graham Cox wrote:
>>
>> I’m
llow
editing, and implement the dataSource methods that update the model for the
edited property.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moder
copied into the editor, you don’t have to do anything.
If it’s not working, you might have done something elsewhere that is preventing
it working as it should.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
view has become
FR? I couldn’t see anything either specific to NSTextView (or NSText) or
views/responders in general. I’d prefer not to have to use a text view subclass
if possible, though if that’s the only way so be it.
—Graham
___
Cocoa-dev
> On 12 Nov 2015, at 10:12 AM, Dave Fernandes
> wrote:
>
> textFieldDidBeginEditing
Sounds promising, but I can’t find that anywhere in the documentation. Where is
it defined? (n.b. I should make clear this is on Mac OS, if that’s iOS only I
can’t use i
> view.
Thanks - I suspected it might be another subclass case. The KVO idea sounds
feasible as well, I’ll look into that.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments t
though it implements the -convertFont:
message, means I don’t get the chance to step in and modify the text view’s
contents in the normal way - I’m going to have to subclass NSFontManager
instead.
I won’t comment on what I think of this architecture.
—Graham
separate out. Just look at NSFontAction to see
what I mean.
—Graham
> On 12 Nov 2015, at 1:07 PM, Ken Thomases wrote:
>
> Probably best to put it in main().
>
> The app delegate is typically instantiated in the MainMenu NIB (or
> storyboard, I guess). Therefore, there
case, NSFontManager doesn’t implement NSCoding so it does not appear to expect
-initWithCoder: anyway.
—Graham
> On 14 Nov 2015, at 9:37 AM, Graham Cox wrote:
>
> Thanks- main() is the only place that works. I tried run() and even init() of
> the application, but even they w
> On 18 Nov 2015, at 11:46 AM, Roland King wrote:
>
>
>> On 18 Nov 2015, at 08:26, Graham Cox wrote:
>>
>>
>> Anyone know what NSFontManager’s designated initializer is?
>>
>> I have set the Font Manager’s factory class to my subclass of NSFon
Yeah, Apple really make it hard to set up older OS installs for dev testing.
If you copy the old installer to the hard disk partition and set it as the boot
drive and reboot, does that work? The installers are (I believe) designed to
run with no OS at all.
—Graham
> On 18 Nov 2015, at
directly, an
observer of ‘thingy’ will be triggered. Is that right?
—Graham
___
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-admins(at
nise
the drive as bootable.
N.B. The USB boot drive even works on a Windows PC to make a “hackintosh”, so
should work on a real Mac.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator co
> On 18 Nov 2015, at 12:30 PM, Graham Cox wrote:
>
> N.B. The USB boot drive even works on a Windows PC to make a “hackintosh”, so
> should work on a real Mac.
>
AHHH!!! I just remembered something. I needed a utility called ‘UniBeast’ to
make the USB stick originally. I
ws the change. The
dictionary is being changed in a KVO compliant way, because the entire
dictionary is updated and replaced as a whole - the settings within the
dictionary are not mutated individually.
—Graham
___
Cocoa-dev mailing list (Cocoa-de
everything, just not all. So if my understanding of KVO
is correct, I now know where to look for these few missing pieces.
—Graham
> On 19 Nov 2015, at 11:38 AM, Quincey Morris
> wrote:
>
> (sorry, posted the incomplete message by accident)
>
> On Nov 18, 2015, at 16:29 ,
dler - you
close the sheet itself by sending -endSheet to the SHEET, not its parent. If
you need to communicate something back to the parent window or code that ran
the sheet, just do it directly from the completion handler. As a block, it can
capture variables from its initiating scope. It’s al
> On 25 Nov 2015, at 4:58 PM, Quincey Morris
> wrote:
>
> n the end, I’ve come to the (possibly incorrect) conclusion, and that Graham
> misspoke.
Yup, I’m a complete idiot. I looked at the docs, saw [NSWindow
-endSheet:sheetWindow] and totally misinterpreted it. I might be
k NSDocument clears its undo state by default on save - looking at my
code, I’m doing this manually (or not, I have a preference for that). Not sure
if that’s pertinent to the discussion, but it may be worth bearing in mind.
—Graham
___
Cocoa-dev mailing
I deliberately DON”T
SAVE. That’s what’s always worked for decades, but now it doesn’t. If you want
to experiment with a change you are unlikely to want to keep, you need to do a
duplicate up front. I just don’t think that’s the way many people’s minds think
about thei
> On 7 Dec 2015, at 2:45 AM, Dave wrote:
>
> On the Mac what is the best control to use to do this?
Just override -mouseDown: in the view and call [NSApp sendAction:toTarget:from:]
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
dislike ‘momentum’, it conflicts with ‘precision’. At least give
your users a way to opt out.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators
rsing deep in the internals of drawing the
popover frame.
It’s not happening on all popovers, but frequently enough that it’s causing me
concern.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
need less complex layout features, you could also do it using Core Text.
But just incremening a string and redrawing it in a textview is really by far
the simplest approach.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
way is trivial, I know, but I don’t see
anything that gives me a displayable path given a URL.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators
Never mind, I just found it: stringByAbbreviatingWithTildeInPath
—Graham
> On 18 Dec 2015, at 8:24 PM, Graham Cox wrote:
>
> Hi all,
>
> I want to display a path to the user. I have a URL, I need to show the local
> file path that represents (it’s always a local fil
subclassing, though you might want to wrap the functionality up
into a view or other class that you can give a string and the teleprinter
effect just magically happens.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do no
> On 19 Dec 2015, at 5:23 AM, Jens Alfke wrote:
>
>
>> On Dec 18, 2015, at 1:24 AM, Graham Cox wrote:
>>
>> I want to display a path to the user. I have a URL, I need to show the local
>> file path that represents (it’s always a local file path), wher
> On 19 Dec 2015, at 7:51 PM, Graham Cox wrote:
>
> But I do want the string to be the most understandable for the user. I don’t
> know really how many average users understand what ~/ means, but it’s
> probably the best I can do.
Actually - heh, -displayNameAtPath: really st
clearer than ~/
So yes, I think this is the right thing after all.
—Graham
> On 20 Dec 2015, at 8:38 AM, Sean McBride wrote:
>
> On Sat, 19 Dec 2015 19:51:03 +1100, Graham Cox said:
>
>> I don’t think a NSPathControl is really appropriate for this.
>
> I'm curiou
I even asking sensible questions? This sort of impedance mismatch usually
suggests a conceptual misunderstanding somewhere, but without a clear
explanation of how colorspaces and bitmaps are used, I can’t see where I may
have gone wrong.
Anyone able to illuminate?
—Graham
s to work efficiently. I don’t need indexed colorspaces,
RGB, CMYK and Gray are plenty enough.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the mod
seems to be that the only sources of these
errors now are Apple’s own code.
—Graham
___
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-admi
my
own, and a few other mods. I’m not sure if Uli is still maintaining this, but
it did the job.
http://www.cocoabuilder.com/archive/cocoa/93982-ann-ukdistributedview-finder-icon-view.html
Uli reads this list, he may be able to tell you the latest news.
—Graham
___
u’ll need to allow for a
slowly moved slider NOT to fire the final message. I typically use 0.1sec.
This mechanism is available to any NSObject, and doesn’t require you to roll
your own timer-based solution. Behind the scenes this is already doing that.
—Graham
__
retriggerable timer” mechanism
available to any NSObject, so it usually makes sense to use it where possible
rather than rolling your own timer or subclassing the control.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not
when a
popover’s edge changes (say from bottom to left and vice versa) but otherwise
my own code has no influence on it.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the
signing issues are always a problem when
they arise because it’s such an opaque procedure which supposedly “just works”
in Xcode. Except when it doesn’t.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or
simply unavailable to non App Store apps? If so it’s not very friendly about
saying so, and also makes it difficult to test the functionality. The app will
go in the App Store eventually, but our testing procedures are far smoother at
this stage (beta) without b
Thank you Quincey!
I was thinking that if Apple want this stuff adopted, they really ought to make
it much easier. Turns out they did :)
—Graham
> On 1 Jan 2016, at 1:39 PM, Quincey Morris
> wrote:
>
>
>
> https://developer.apple.com/library/mac/documentation/
to follow
suit.
Since 10.11 changed how this works, I’d expect to see an explanation at least
in the release notes, but I don’t see anything there. Is there any other info
about this? The docs as usual are ambiguous and self-contradictory.
—Graham
> On 1 Jan 2016, at 5:59 PM, Graham Cox
you can’t attach images to emails on
this list).
—Graham
___
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-admins(at)lists.apple.com
Help/Un
le,
but people always whinge about it. That’ll shut them up even though it’s always
been for their (and my) own good (i.e. readability).
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
ferent fron the ‘pixelsWide' and
‘pixelsHigh' properties. The ratio of these defines the resolution.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact th
e exact same
place on the screen. Trouble is, I just can’t get that to work.
I’m missing something about how to correctly translate coordinates between two
separate windows.
If anyone can spell it out step by step that would be great - I just can’t see
where my thinking is faul
oPoint:, -setBoundsOrigin:, -scaleUnitSquareToSize: and so on
- these seem likely candidates, but I’m no sure quite where to set these up.
I’ll experiment…
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post
lues, but
instead make the view match the original coordinates so I can draw using them
unmodified.
In fact this is now 90% working, it’s just the refresh that’s out of kilter,
which is no surprise since the CTM is only modified when drawing. I think I’m
close….
—Graham
__
that will work across
any number of screens, and also back to the older OS versions? (10.7 at least).
—Graham
> On 16 Jan 2016, at 5:19 PM, Graham Cox wrote:
>
> In fact this is now 90% working, it’s just the refresh that’s out of kilter,
> which is no surprise since the
w. It might not matter, but for big graphs (10,000+ objects)
it can be a killer. If any setters have side effects it can be suicidal.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comme
ary
format, so yielding an archive file that is somewhat human-readable, though
it’s not in any standard format (other than XML itself) and can become much
larger than the equivalent binary file.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@
generally think this is
worth doing?
—Graham
___
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-admins(at)lists.apple.com
Help/Unsubscribe
]
URLForDirectory:NSDesktopDirectory inDomain:NSUserDomainMask
appropriateForURL:nil create:YES error:&error];
I can’t see any obvious difference between the URL here and the one I get from
NSOpenPanel, but there must be one.
Any ideas what the problem could be here?
—Gr
__65-[MDABExportController
beginSheetExportOperation:onParentWindow:]_block_invoke + 449
(MDABExportController.m:104)
Sandboxing issues are bad enough to deal with, but when they bleed over into
‘open’ apps that’s just nasty.
—Graham
> On 28 Jan 2016, at 2:05 PM, Alex Zavatone wr
user’s iCloud documents. I thought that setting allowed this
without sandboxing, not that it snuck sandboxing in by the back door. I will
check and see whether that’s a red herring.
—Graham
> On 28 Jan 2016, at 2:41 PM, Roland King wrote:
>
> have you checked your info.plist fil
ndboxed when it has no resources indicating
that it is? Does the OS cache info anywhere about this? The app *has* been
sandboxed in the past during development, so wondering if there’s some info
cached somewhere that needs clearing?
—Graham
___
Co
> On 28 Jan 2016, at 4:36 PM, Graham Cox wrote:
>
> Why would the OS think an app was sandboxed
OK, I think I found the problem. In Build Settings->Code Signing, the “Code
Signing Entitlements” was set to a .entitlements file which is actually nothing
to do with this product.
we’ll need
it to work sandboxed as well as unsandboxed, so now we’ve defaulted to a folder
we make inside ~/Documents, and also added a checkbox (on by default) that
reveals the written files in the Finder so that they can’t really miss where
they went.
—Graham
___
s to the program I am building so
> that it knows what the lights actually mean.
Presumably the self-driving car folks have solved this one. If not, we’re in
trouble…
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do no
standard NSView? (MacOS)
A similar requirement applies to CALayer too.
—Graham
___
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-admins(at
> On 3 Feb 2016, at 5:05 PM, Graham Cox wrote:
>
> Is there a good way to automate this for a given set of properties?
BTW, it would be really great if this were an extension of property attributes,
e.g:
@property (nonatomic, assign, refresh) BOOL goesWild;
Then the c
Rect calls and
MY_IDLE_TIME has elapsed
….
}
—Graham
___
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-admins(at)lists.apple.com
Help/Uns
is done’ is not a requirement. I’ve
written hundreds of specialist views for many different purposes, and never had
to do this.
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the
1 - 100 of 3976 matches
Mail list logo
