2011/9/25 Vojtěch Meluzín meldaproduct...@gmail.com
Hi,
I'm creating a GUI system for AU/VST plugins. The host creates the view and
the rest is based of modal windows, so I'm using NSApp runModalForWindow
for
that. But there are a few problems:
1) NSApp runModalForWindow does not activate
Hi,
In an application I am developing, complete App wide tooltips start to
misbehave after some time (not able to reproduce the exact steps). The
tooltips flicker and then disappear. This also gets randomly fixed (no
specific steps).
This is happening in both in Mac OS X Leopard and Snow Leopard.
Is there any way to detect if an application is in modal session?
I am trying to fix (work around) a problem in Cocoa + Carbon application,
where Cocoa UI thread is not blocked(for some Cocoa views) when a modal
dialog is invoked from Carbon app.
Thanks,
Vijay
Even if you compile your application with Mac OS X 10.4 project settings.
The app when run on Mac OS X 10.5 will have full access to 10.5 SDK.But
reverse is obviously not true.
For example: If a method of a class is only available in Mac OS X 10.5 then
you can write your code such that the method
Hello All,
Is there a way to disable all tooltips in an Application.
Regards,
Vijay
___
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
This won't work because it doesn't know who should become the responder
when it resigns. Instead, if you make some other object (window) key, this
one should lose that status. (i.e. it can only jump if it has somewhere *to*
jump).
The next object in responder chain should become first
This won't work because it doesn't know who should become the responder
when it resigns. Instead, if you make some other object (window) key, this
one should lose that status. (i.e. it can only jump if it has somewhere *to*
jump).
The next object in responder chain should become first
Peter. Yes, bracketing the calls removes the flicker. But as far as the
correct solution goes:
There might not be any other window which I should make key. In that case
the panel should simply resign the key focus and let application handle the
events.
It seems this will be the solution for now.
On Tue, Jun 10, 2008 at 7:54 PM, Adam R. Maxwell [EMAIL PROTECTED] wrote:
On Jun 9, 2008, at 11:17 PM, James W. Walker wrote:
On Jun 9, 2008, at 10:44 PM, Joseph Kelly wrote:
Toggle the release when closed setting on the window nib? See the docs
for -[NSWindow setReleasedWhenClosed:]
Not sure if this is possible without installing development tools.
However you can try using Sample in Activity Monitor(App/Utilities) on the
hanged app.
(Double Click the hanged app in Activity Monitor to get console window and
hit Sample)
Thanks.
- Vijay
On Fri, Jun 6, 2008 at 4:43 PM, parag
may also try exploring any 3rd party tool for
this.
- Vijay
I need to find out the statement no. which is causing the application
hanged. I have built the application in Debug mode.
Thanks,
Palav
On Fri, Jun 6, 2008 at 4:52 PM, Vijay Malhan [EMAIL PROTECTED]
wrote:
Not sure
On Fri, Jun 6, 2008 at 9:41 PM, Jon Keon [EMAIL PROTECTED] wrote:
Hi All,
I'm having a problem with creating new instances of classes after other
instances of them have been released.
I have a class called BaddieManager.
In this class I have a NSMutableArray that holds instances of
. Thanks.
Link:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaFundamentals/CocoaDesignPatterns/chapter_5_section_4.html
- Vijay
Thanks,
Jon
*From:* Vijay Malhan [mailto:[EMAIL PROTECTED]
*Sent:* Friday, June 06, 2008 1:48 PM
*To:* Jon Keon
*Cc:* Cocoa Developer List
On Thu, Jun 5, 2008 at 9:47 AM, Graham Cox [EMAIL PROTECTED] wrote:
In my app I'm getting a hang when my main document window is asked to
close. This occurs only if there are unsaved changes, but it hangs before
the unsaved changes sheet is presented.
If I link against the 10.4u SDK (but
On Thu, Jun 5, 2008 at 12:51 PM, parag vibhute [EMAIL PROTECTED]
wrote:
Hi all,
I have implemented Cocoa application where I am handling exceptions through
signal handling.
I went through the Apple TechNote TN2123 (
http://developer.apple.com/technotes/tn2004/tn2123.html). It states
In XCode, Drag your dylib to the Link with libraries group under
your app target. You may also want to add your dylib target as a
dependency to your app.
- Vijay
Sent from my iPhone
On 05-Jun-08, at 4:33 PM, Damien Cooke [EMAIL PROTECTED]
wrote:
Hi,
Here is a dumb question for you :)
On Fri, May 30, 2008 at 1:26 PM, haresh vavdiya
[EMAIL PROTECTED] wrote:
Ya but i have retained my stringRes instance variable but i can't
understand
what is problem
We can't see that in your code.
Use: self.stringRes = txtResult.text;
and declare a retain-property for your string ivar. or
An Example:
mTable = member instance for your TableView
mData = member array which provides the data-objects.
Put the following code at a place where your table and data-source array is
initialized. Like in awakeFromNib: method.
Here I'm sorting on key name, Change it to whatever key you
On 23-May-08, at 7:41 PM, Jordan Woehr wrote:
First, I sent this once but I don't think it made it onto the list.
I've
done a quick search of the archives and couldn't find it. I
apologize in
advance if this end up being a double post.
Hi everyone,
I'm trying to write a bilateral filter
We are not allowed to talk in public about the iphone apisyet..Is
called DNA
Well, no, it's called NDA, which stands for non-disclosure agreement.
It's that pesky legal contract you agreed to in order to gain access to the
iPhone SDK that says DO NOT TALK ABOUT THE SDK UNTIL IT IS
Savant,Right, coming back to that, my actual question to the forum was that
If I can write my own framework and deploy it on an iPhone. I was not
discussing about any of the API so far, so I was not violating any
agreement/contract.
I got my answer from the SDK Agreement itself (Section 3.2.2-
Savant,Right, coming back to that, my actual question to the forum was that
If I can write my own framework and deploy it on an iPhone. I was not
discussing about any of the API so far, so I was not violating any
agreement/contract.
I got my answer from the SDK Agreement itself (Section 3.2.2-
You are not retaining the autoreleased array in your constructor. You
are over-riding the first initialization of your array(which is a
leak) while you are initializing with arrayWithObjects: call.
You can remove this line completely
cityArray = [[NSArray alloc] init];
and do a retain on
Are you on Leopard?
This behavior should not be there on Tiger.
I faced similar problem on Leopard with NSTableView. It seems in
Leopard, nib is loaded, with lazy-loading kind of approach. The
controls are not initialized until the window, on which the controls
are hosted, is not
.
You might wanna a file a bug for this on Apple.
- Vijay
On 21-May-08, at 10:56 PM, Torsten Curdt wrote:
On May 21, 2008, at 19:21, Vijay Malhan wrote:
Are you on Leopard?
Yepp!
This behavior should not be there on Tiger.
I faced similar problem on Leopard with NSTableView. It seems
Yes you are right. If we see this as an optimization enhancement, it
completely make sense to have things work like this. But my point is
that this behavior is not in-sync with the Leopard framework
documentation (XCode 3.0) and Tiger implementation. Following is
extract from the Mac OS X
On 21-May-08, at 11:37 PM, I. Savant wrote:
Consider +(void)initialize ... also, *none* of them are
initializers by implication because they're class methods.
Sorry, these two sentences seem to be contradictory. Let me clarify:
+initialize is used to initialize the *class*. No class
in above example is not valid.
Thanks in advance.
On Thu, May 22, 2008 at 12:30 AM, Shawn Erickson [EMAIL PROTECTED] wrote:
On Wed, May 21, 2008 at 11:47 AM, Vijay Malhan [EMAIL PROTECTED]
wrote:
What exactly do you mean by initializing the *class*? what exactly
is
initialized
28 matches
Mail list logo
