o, you should still file a
formal bug report. Don't forget to include information about the
version of Mac OS X and Xcode that you're using.
Thanks,
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin r
nd XCode 3 until I modified it.)
I am just getting used to IB3 but don't see what or how I could have
broken the connection. Are there any obvious culprits?
Double-check that the "window" property of the window controller
(files owner) is connected to the window in
On May 18, 2008, at 3:46 PM, Hal Mueller wrote:
-validateMenuItem: is deprecated
Really? Where is this documented?
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the
reat to have an
influx of new people come with fresh ideas. Please file bug reports
for any concrete problems you find or suggestions that you have:
<http://developer.apple.com/bugreporter/>
j o a r
___
Cocoa-dev mailing list (Coco
isplay you should call -display, but you
should only have to do this in exceptional situations. It is much more
common to flag a control as needing to update display, in which case
you would call -setNeedsDisplay:. In this case though, you shouldn't
have to do either, as the call
to re-visit this discussion one to two years from now. I
don't think that it's fair of us to expect you to provide an informed
comparison before you have more experiences with both environments.
Regards,
j o a r
___
Cocoa-dev mailing lis
essage to this thread:
We welcome input from new users to our platform. It's great to have
an influx of new people come with fresh ideas. Please file bug
reports for any concrete problems you find or suggestions that you
have
j o a r
_
pple's installer:
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/PackageMakerUserGuide
>
<http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareDistribution
>
j o a r
___
Cocoa-dev mailin
if you're using a
text cell, an image if you're using an image cell, and so on.
The reason for using "id" here is to allow you to use any type of
object value as the source of data for your cell to display.
j o a r
___
Co
ay
to convert NSPathStore2 to an NSString?
How do you determine that this is a problem? What is the 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.
Conta
set to the current date and time."
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/Unsubscr
.
Why not simply:
[[self superclass] instancesRespondToSelector:...]
?
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-de
quot;, [inObject valueForKey: @"selection"]);
dumps:
selection: <_NSControllerObjectProxy: 0x177cb0>
But if I change it to @"selection.number", it throws the exception:
"[ valueForUndefinedKey:]: this class is
not key value coding-compliant for the key
d re-examine your design if you find
that to be a problem in practice:
<http://en.wikipedia.org/wiki/Code_smell>
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to
ike a window controller.
You would also typically set the data source in IB, and not in an
action method.
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.
Contac
On Jun 1, 2008, at 5:56 PM, Nick Rogers wrote:
How can I make changes to the default "about panel"?
Or do i have to add my own panel?
Have a look at this technote:
<http://developer.apple.com/technotes/tn2006/tn2179.html>
j o a r
__
non-retaining array class or come up
with another solution to this problem? Or is there anything in
particular I should watch out for when subclassing NSMutableArray?
If you're only targeting Leopard or later, you might want to take a
look at "NSPointerArray&q
the tip!
It is pretty awesome. It was introduced together with the new
NSMapTable and NSHashTable classes [*], primarily to support using
Cocoa together with Garbage Collection.
j o a r
[*] Not to be confused with the older C-API with the same name
_
ready immutable, this is typically cheap. See the
"Copying Mutable Versus Immutable Objects" optimization here:
<http://developer.apple.com/documentation/Cocoa/Conceptual/MemoryMgmt/Tasks/ImplementCopy.html#//apple_ref/doc/uid/20000049-9
load this debug menu from a nib file, but I would probably
suggest that you just create and insert it programatically. See the
API in NSApplication (for how to get a reference to the main menu),
and the API in NSMenu & NSMenuItem (for how to create and insert the
acktrace in the thread list. That
would tell you where it's hanging.
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)l
In some
instances, I've found that tracking down a header file and
#importing it sometimes gets rid of the message, but not always
(can't seem to get rid of the three shown here, ever.)
These are all methods added in Mac OS X 10.5. Check the SDK settings
for your target.
j o a r
__
.)" expression is
found, while -Wselector only performs its checks in the final stage of
compilation. This also enforces the coding style convention that
methods and selectors must be declared before being used.
j o a r
___
Cocoa-dev mailing
e browser for performance reasons by default use an
existing embedded thumbnail / preview to improve perceived performance.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to
See:NSCollectionView
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 Subscri
gthy routine thread safe, and if so, run
it on a background thread.
You should put a lot of effort into always leaving the main thread
open for user events.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post adm
e
safe", to invest your time in a multi-threaded implementation.
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.app
and, indeed, fraught with peril.
Do you feel the same way about passing a (char *) to a method that
takes a (const char *)?
I think that it's perfectly reasonable to expect the receiver of the
piece of data, or object, that you hand over to respect the basic
restri
ation.
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 Subscrip
e there are some operations on the NSView
class that are thread safe, 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
#x27;d suggest that this is a design flaw that you
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 pos
documentation fix I'd
suggest that you contact ADC and ask for an update. There might be
some sort of misunderstanding:
<http://developer.apple.com/contact/>
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
till not thread
safe, can be used from different threads - As long as they're only
ever used from one thread at a single time. Et.c., et.c.
The complexity of this topic makes it difficult to create the same
type of documentation that we enjoy for the simple API r
lay sound files
asynchronously.
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/Unsubscr
<http://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
n/window?
Can you explain what you mean by that?
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.co
cally 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
to have 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
y 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
ggest 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
ppear "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 alw
create a complex
custom cell 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 t
ith Cocoa / Objective-C development in practice.
Most Cocoa 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
___
uired
though: Xcode and IB are now on better speaking terms, so you don't
have to manually tell IB to read header files for it to learn about
changes to classes in the project, it stays up to date automatically.
j o a r
___
Coc
o the responder chain, in
that case typically right after its view.
But if my design explicitly specifies the target (connecting
IBActions in InterfaceBuilder), I dont have to worry about the
Responder chain for actions. Correct?
Correct.
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.
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
- Using the "dataSource" property of the table view. At
this point it sounds like a good thing to double-check that this
connection is set up properly in IB.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not
want to verify, at runtime, that this connection is set. You
can do this either in the debugger, or just using a standard debug log
statement.
Btw.: Have you set up any bindings for this table view?
j o a r
___
Cocoa-dev mailing list (Cocoa-dev
view (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 l
"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 t
t;main" and "key"
window is in Cocoa). You could find 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 a
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&quo
er 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
ly a bug - most 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 ad
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
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.
imply 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-admi
eData
API:s that might provide some / all of what you're looking for.
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
tor:" (note 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/Unsubs
a look 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
.
There is a GCC warning to help you 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
im
ation
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/Unsubscr
w overlapping views are supported. Why isn't
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://devel
kyClass KVO
observer 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
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
also allows control 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
__
pplications based 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.
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
ntegerMax.
This is how you print a NSUInteger:
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
animation 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 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]"
P. And if I move those methods 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
rive UI updates based
on KVO 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 mod
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
ed 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
-piece. You
typically don't want to load all of it into RAM at once.
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-admi
ppearing, but I can't find an easy way to
avoid deferring some operations.
How about delaying adding the control until the value you want to
display in the control is "ready"?
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.
ion scheme to supplement
this method?
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/Unsubscr
gt;
<http://developer.apple.com/documentation/Cocoa/Conceptual/Documents/Tasks/ImplementingDocApp.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 modera
eView and override "-keyDown:". There should be several
implementations of this online that you could take a look at.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comme
instances that are strongly typed
(NSFileManager, NSHost, NSNull, et.c.).
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
acter" and similar in NSText.h (and 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 to the list.
Contact the moderators at cocoa-dev-admins(at)lists.
1/7/16930>
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
Reference/FSEvents_Ref/FSEvents/index.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)lists.apple.com
Help/Unsubscribe
ehind the scenes, but it's one way to get an
understanding. (Also
add an override for autorelease.)
A much, much, better way of doing that would be to use the Object
Allocations instrument.
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@l
Chuck,
* You really shouldn't suppress these warnings
* If you use ObjC 2.0 properties you don't have to write those
accessors in the first place, and
* If you use ObjC 2.0 properties, you can use this form without
warnings:
self.foo = foo;
j o a r
On Mar 23, 2008,
ngleton objects should never be released");
[super dealloc];
}
This communicates better what your intention is, and also catches the
unlikely case of this instance ever being deallocated when it
shouldn't, or if the class is being repurposed to a multi-inst
then only actually update the behaviour for apps compiled on a
newer version of the OS.
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 c
dates. You
might need to throttle or otherwise limit your callouts to the main
thread if this proves to be the problem.
You can use Instruments or Shark to get a view of the work being
performed on the main thread while you run your worker thread.
do
*something*...
How do you notify the controls in the UI that they need to update to
reflect new values?
What is the total time required to run the task by your worker thread?
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
time by not learning how to use the
performance tools.
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.app
, for us to be able to help you
figure out what's wrong.
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.appl
ssBar, [value doubleValue]);
[progressBar setDoubleValue: [value doubleValue]];
}
Like I said earlier, I think that you would benefit from posting a
sample project that reproduces the problem.
j o a r
___
Cocoa-dev mailing list (
s for me please as I think I'm going mad.
Sounds like some sort of conflict with keyboard shortcuts used by menu
items in the main menu?
(g -> find next, p -> print, q -> quit, et.c.)
j o a r
___
Cocoa-dev mailing list
entation:
<http://developer.apple.com/bugreporter/>
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
He
#x27;s
obviously also a really good place to learn more about our tools - and
everything else related to development on the Mac.
Cheers,
j o a r
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moder
ide of the class
No, ObjC doesn't have any support for static member variables.
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 coco
On Apr 10, 2008, at 12:48 PM, j o a r wrote:
No, ObjC doesn't have any support for static member variables.
Btw. For ObjC I think it would be more appropriate to call them "class
variables".
j o a r
___
Cocoa-dev mailing
would be a very cool
addition), you basically have to do it manually.
NSString has a method to help you identify line endings in case you
have to deal with files that could use different characters /
character sequences to represent that (\n, \
1 - 100 of 197 matches
Mail list logo
