/NSCollectionView_Class
j o a r
___
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/Update your
that you're interested in keeping
alive.
j o a r
___
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
not
asking. Could you perhaps explain what you're really trying to do?
Cheers,
j o a r
___
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
views will be redisplayed
at the end of the current event loop. This leads to less flickering,
and less redundant redrawing.
Like I said in my last reply to you: We can't really help you before
you tell us what you're *really* trying to do.
j o a r
(readonly) Direction currentDirection;
@end
Your observers would add themselves as observers for the properties
that they are interested in, and then get notified as they changes. I
think that these three properties would be all that you need to
satisfy your #1 - #3 above.
j o a r
the collection in such a way that you
get the KVO behavior that you need.
j o a r
___
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
manually (unlikely), make sure that you
understand the arrangement of views inside the scroll view first.
There is a very good scroll view programming guide in the
documentation that can help you get up to speed.
j o a r
___
Cocoa-dev mailing
On Jan 7, 2009, at 1:26 PM, j o a r wrote:
// A suggestion
The correct thing to do is typically not to start with a scroll
view. If you simply drag out a text view from the library it comes
wrapped in a scroll view already - No need to add a scroll view
manually.
If you need to set it up
On Jan 7, 2009, at 1:42 PM, David wrote:
Hello,Is there a way to obtain the icon that finder uses to display
for a
file system object? Such things as the folder icon for folders, PDF
icon for
pdfs etc.
See: NSWorkspace
j o a r
using custom
artwork in this case.
j o a r
___
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
(using local autorelease
pools, or even sidestepping the user of autorelease).
j o a r
___
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
, the documentation and
sample code that is provided should be able to provide better guidance
for how these properties work (or don't).
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
can provide a screenshot of what the toolbar
looks like when it's not aligned properly? If you could post a sample
project that reproduces your problem, that would probably help too
(preferably over http, and not inline to the list).
j o a r
of defensive memory management scheme. Increasing retain count is
NOT a way to become thread safe.
On Dec 25, 2008, at 11:49 PM, Scott Wilson wrote:
Am I missing something?
I don't think so.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev
an explanation or tell me how to solve it?
From the documentation for this method:
A new string made by removing from both ends of the receiver
characters contained in set.
Note that it only removes characters from both ends of the receiver.
j o a r
starting with Mac OS X 10.5 Leopard.
j o a r
___
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
you will see exactly who
called it in the call stack. You can then go a figure out if that
was on purpose.
Don't do that - Use the ObjectAlloc Instrument, it provides this
information out of the box.
j o a r
___
Cocoa-dev mailing list (Cocoa
://developer.apple.com/documentation/Cocoa/Conceptual/ControlCell/Tasks/SubclassingNSCell.html
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators
be appreciated.
Take a look at this sample project:
http://developer.apple.com/samplecode/PhotoSearch/
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
On Dec 8, 2008, at 4:43 PM, Chris Idou wrote:
Is there any Cocoa API which returns the environment as a
NSDictionary, or do I need to drop down to the UNIX getenv() level?
See:
-[NSProcessInfo environment]
j o a r
___
Cocoa-dev
a run loop to do
this. Thanks.
Perhaps if you'd tell us why you'd want to do this, we might be in a
better position to offer good advice.
Thanks,
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin
initialized.
j o a r
___
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/Update your Subscription
that you have problems. I suspect that we will
figure out what's wrong, and that you will be able to fix it easily
and then move on.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
machinery that the
numberOfStudents property depends on the count of objects in the
array. See:
http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueObserving/Concepts/DependentKeys.html
j o a r
___
Cocoa-dev mailing list (Cocoa-dev
On Nov 28, 2008, at 2:49 PM, j o a r wrote:
I think that it would be more straight forward and efficient to
write that:
[NSString stringWithFormat:@The number of students is: %lu,
((unsigned long)[theStudentArrayController count])];
Crap, typo: You'd get the count from the array
/documentation/Cocoa/Reference/CocoaBindingsRef/Concepts/BindingTypes.html
j o a r
___
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 the CIColorTracking sample code:
http://developer.apple.com/samplecode/CIColorTracking/index.html
Very interesting stuff. Also highly efficient, since it's typically
hardware accelerated.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev
provided by Mac OS X and our developer
tools. For more information, see the 64-bit transitioning guides.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
the implementation
of the property setter method - A subclass could for example override
it and make it not safe for use from init / dealloc.
That said, this might be something that the LLVM static analyzer could
validate for us to the point where it would be OK.
j o a r
on
this behavior.
Please file bug reports whenever you find that our sample code and
documentation are in conflict!
http://developer.apple.com/bugreporter/
Thanks,
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com
to still use them.
j o a r
___
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/Update your Subscription
on the autorelease pools higher
up in the stack.
j o a r
___
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
that we often add to manual accessors.
j o a r
___
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
that Microsoft has moved away from code generation with
their recent WPF designers that uses XML for storage.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
this be
fixed to be fully supported and robust? Of course. If you care about
this, I'd suggest that you file bug reports.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
) window and
setDefaultButtonCell:[btn cell] on it, then the window hangs when it
opens
It waits on a semaphore in NSViewHierarchyLock from the view and
windows's displayIfNeeded code, all from within the runModalForWindow.
What thread is this being run on? Do you have a run loop?
j o
is the Darwin room in Building 1 (sorry for the lack of map here).
We're not allowed to record video or audio for this event, so if you
want to see it, you have to come down in person. See you there.
=
And, don't forget NSCoderNight in Campbell tonight!
Cheers,
j o a r
of the window?
j o a r
___
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/Update your Subscription
so that I copy
one file at a time in some method invoked off the run loop, while
allowing the UI to continue to run and cancel, setting some flag I
check.
No, you should use a background thread. Trying to perform the work
piecemeal on the main thread will result in a bad user experience.
j o
for the panel, which gets ugly.
Why do you need a subclass of NSWindow in the first place?
j o a r
___
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
is doing.
Why would mouseMoved needs fixing at the window level? What problem
were you trying to solve when you created your window subclass?
I'm not asking to put you on the spot, but rather to figure out if
there's some other, possibly even better, way to do this in Cocoa.
Cheers,
j o
.
GuardMalloc: - Applications using vector instructions (e.g., SSE
or Altivec) should work.
GuardMalloc: GuardMalloc version 18
You have enabled GuardMalloc in Xcode. If you don't know what it is,
you probably want to disable it again. See:
Xcode Run Enable Guard Malloc
j o a r
/uniformtypeidentifiers.html
http://developer.apple.com/documentation/Carbon/Conceptual/understanding_utis/understand_utis_intro/chapter_1_section_1.html
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
, but the human readable
description would be returned by:
UTTypeCopyDescription()
What is the problem that you're really trying to solve here? It might
be that there is a better way of going about what you're trying to do.
j o a r
___
Cocoa-dev
defaultParagraphStyle] fits this
pattern, since it returns a shared instance.
j o a r
___
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
I've solved that problem in the
past.
If you'd like to see this capability added to NSWindow, I suggest that
you file an enhancement request. It will be flagged as a duplicate,
but it would still be useful - by showing interest, it's more likely
that it will be prioritized.
j o a r
recently is not for lack of
trying, there has just been a number of unfortunate roadblocks. We're
hoping to have a new event in the next couple of weeks. Stay tuned.
And yes, the CocoaHeads mailing list is probably better for questions
like this one.
j o a r
almost always
the case that you'll end up surprised by what you find! We also often
forget to do #4, something that typically leads to maintenance
problems later on.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
that are still in use. how do I
determine what is a leek and what is not ?
Put a log statement in their dealloc methods to verify that they're
actually being deallocated.
NSLog(@Dealloc: %@, self);
False positives from Leaks should be rare, but I'm sure that it can
happen.
j o a r
a bit more information:
Is var1 an instance variable or local variable? How was the original
value of var1 assigned? Is the object returned from -message
autoreleased? Can you provide more code from the actual implementation?
j o a r
___
Cocoa-dev
= [self giveMeAString];
[aString retain]; // String retained here, but never subsequently
released. This is a leak!
}
Notice how the string is created in one place, but how the actual
memory management error that leaks that object happens elsewhere.
j o a r
identifier.
j o a r
___
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/Update your Subscription:
http
is precisely zero.
I never claimed that my opinion represents what is in use, quite the
opposite: See my original reply in this thread. I'm arguing for what I
consider to be *better*.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com
Hello Brian,
I hope that you've filed a formal bug report? If not, that should be
your first priority in a case like this:
http://developer.apple.com/bugreporter/
Thanks,
j o a r
On Oct 9, 2008, at 10:47 AM, Brian Miller wrote:
I have a Cocoa Core Data Document based
do?
Most apps use just the name, but I've never liked that and I support
your idea of using the bundle identifier. Makes a lot of sense.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests
like for menu items.
j o a r
___
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/Update your
facility for troubleshooting that type
of problem, but in this case you could probably do with simple code
inspection.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
be interesting to know how you find memory leaks.
j o a r
___
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
of NSString.
j o a r
___
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/Update your Subscription:
http
call is introduced.
j o a r
___
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/Update your
. not by you, as the retain count of an object reaches
zero.
j o a r
___
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
into the
main implementation of the class, it all works out. Any idea why is
that? Thanks for your help. BR, Pan
Perhaps a memory management error somewhere? Try to run your app with
NSZombieEnabled (Google for the details) and see what that turns up.
j o a r
notifications from non-main threads. Could this be your problem?
j o a r
___
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
that all users
are running the same email client.
There are some third party attempts at solving this problem - Google.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
to forward your UI updates to the
main thread. That's typically easy to do using
performSelectorOnMainThread:
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
or flickering though.
You would have to resize the window manually. To find out how to size
and position it, ask NSScreen for the appropriate frame. To avoid
flickering, do this in awakeFromNib or similar, before the window is
put on screen.
j o a r
On Sep 20, 2008, at 11:11 AM, Benjamin Stiglitz wrote:
Alternatively, you can set its frame to [[window screen]
defaultFrame], which is the same frame
that -zoom: will use, subtracting space for any visible drawers.
I think that should be:
-[NSScreen visibleFrame]
j o a r
:
NSLog(@NSUInteger: %lu, ((unsigned long)counter));
j o a r
___
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
On Sep 13, 2008, at 1:43 PM, Markus Spoettl wrote:
Not true, I can think of many scenarios where you have no other
choice.
Like what? Seth is right in general, app termination is very much a
special case.
j o a r
___
Cocoa-dev mailing list
on the
Application Kit, so your code normally does not have to deal with them.
On threads that you set up, you have to manage the top level
autorelease pool manually.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
On Sep 2, 2008, at 12:55 AM, Roger Herikstad wrote:
Since the Carbon stuff is not 64 bit
Not correct: Some of it is, some of it isn't. Read the API reference
documentation and release notes to figure out which is what. Besides,
QTKit is a Cocoa framework.
j o a r
of the QTMovie idle state.
http://developer.apple.com/technotes/tn/tn2125.html
I'm not an expert on this - you might want to consult a QT specific
mailing list for a definitive answer.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com
context. After all there's no penalty for being verbose in
this case. Of course using a pointer to a global solves this too.
The penalty for using constant strings is that they will end up
wasting space in your binary...
Rons suggestion is probably optimal.
j o a r
this documented? Can we rely on overlapping sibling views working
now and in the future? Are there any caveats we should be aware of?
Hello,
Please file a couple of bug reports on this:
http://developer.apple.com/bugreporter/
Thanks!
j o a r
in this particular case.
j o a r
___
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/Update your Subscription
with that, but in addition, you can
learn to type:
if (nil == foo)
Problem solved! :-)
I personally much prefer to have if-statements that clearly evaluate
to a boolean value. More intention revealing, and to me that's more
important than being terse.
j o a r
at this:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaBindings/Tasks/masterdetail.html
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
the trailing :).
j o a r
___
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/Update your Subscription:
http
one,
perhaps not even primarily one, of performance considerations.
j o a r
___
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
one. Moreover, the Xcode-style of auto-implement is
exactly what I want. This feature can improve the efficiency and
productivity of users greatly.
Have a look at the NSTextView -
textView:completions:forPartialWordRange:indexOfSelectedItem:
delegate method.
j o a r
describe your application, and your use of nib files, it might
be that we could provide some suggestions for cutting down on that
number.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator
likely a very well known bug.
You might still want to file a bug report to indicate interest in
getting this API fixed for some future release.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests
is: It
depends.
If you're using GC, you wouldn't have to remove the observer. If
you're not using GC, you would.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
On Jul 18, 2008, at 11:51 AM, Andy Lee wrote:
I don't see the difference from the caller's point of view.
There isn't any, and that was not MMalcs point. His point was that you
were using the term autoreleased incorrectly.
j o a r
___
Cocoa
that document like this:
NSApp Main Window Window Controller Document
j o a r
___
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
of daemon-safe frameworks:
http://developer.apple.com/technotes/tn2005/tn2083.html#SECLAYEREDFRAMEWORKS
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact
(shouldn't be
that
hard), but interface builder manages to do it between objects that
aren't
connected by ANY view, and I am not sure how to do that.
IB probably uses one or more separate transparent windows to hold the
connection lines.
j o a r
think that would be considered a bug in IB 3, and not an expected
side effect. If you can verify that this is the case, and in
particular if you can reproduce the problem, you should file a bug
report here:
http://developer.apple.com/bugreporter/
j o a r
into? What is best?
There is no way to do that in IB, you would have to set up the timer
in code, but that's easy enough - Check the documentation for the
NSTimer class. What are you going to use the timer for? There might be
something else that would be better for you to use in Cocoa.
j o
developers will find that Garbage Collection works
absolutely fine, and that runtime performance is about the same
(sometimes better, sometimes worse) compared with using manual memory
management.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev
subclass:
http://developer.apple.com/samplecode/PhotoSearch/
j o a r
___
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
active while
actually being hosted by a background application. As such, the
progress indicator in one of them is grayed out, how do I prevent it
from doing that?
Create a custom NSWindow / NSPanel subclass that overrides -
isKeyWindow to always return YES.
j o a r
a bundle. You
can just store the image data as files in the file system.
I'm also curious as to why you decompress the JPEG file? If you got
the image as a compressed JPEG, why not store it as is?
j o a r
___
Cocoa-dev mailing list (Cocoa-dev
by the user?
It sounds like you go from JPEG - NSImage - NSData? Instead of
creating a NSImage, how about just storing the JPEG as is to the file
system first, and only later generating NSImages as needed for display
in your application.
j o a r
that you intercept the drag operation and copy the
file directly. You should be able to do this quite easily if you
subclass the image view:
http://developer.apple.com/documentation/Cocoa/Conceptual/DragandDrop/DragandDrop.html
j o a r
___
Cocoa
constrains
itself to the screen.
http://developer.apple.com/documentation/Cocoa/Conceptual/WinPanel/Tasks/SizingPlacingWindows.html#//apple_ref/doc/uid/2228-135785
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post
://developer.apple.com/documentation/Carbon/Reference/QuartzEventServicesRef/Reference/reference.html
I assume that you've already familiarized yourself with the
Accessibility APIs:
http://developer.apple.com/documentation/Cocoa/Conceptual/Accessibility/cocoaAXIntro/cocoaAXintro.html
j o a r
. The OS prevents you from interacting directly with the
internals of other applications for stability and security reasons.
You should be able to do what you want using Quartz Event Services.
Is there a way to build a focus-less application/window?
Can you explain what you mean by that?
j o
, that doesn't mean that subclasses have
even the same level of thread safety - unless explicitly called out in
the documentation.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments
should fix. The view objects in your application should not double as
model objects - See: The MVC design pattern.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list
1 - 100 of 169 matches
Mail list logo
