On May 16, 2011, at 8:11 AM, Bill Cheeseman wrote:
When I quit and relaunch the application, the animations sometimes don't run
for the full specified duration when I hit the hot key. During any given run
of the application, the animations either work correctly every time I hit the
hot
I understand this is not the way to close an application, but once someone does
use the red dot, is there a way to get the program out of the background and
back on the screen?
JIM ROGERS
jimrogers_w4...@me.com
http://web.me.com/jimrogers_w4atk
___
Jim
Do you realise that this is a mailing list for software developers?
Nonetheless, assuming you don't mean programatically, simply click on the
application in the Dock.
Joanna
--
Joanna Carter
Carter Consulting
___
Cocoa-dev mailing list
I am a cocoa developer, albeit a new one. So I have every right to post this
question on this site. Thank you very much, but clicking on the application in
the dock does not work in my case. That would be a rather obvious answer and
one of the many things I tried. Based on some of the web guru
when you 'close' the window - by default the application is not being
terminated - you can get your window back programmatically by calling
[myWindow makeKeyAndOrderFront].
This is what some apps call, when you click their icon on dock to get
the closed window back.
You can legally terminate
JAMES ROGERS jimrogers_w4...@me.com writes:
I am a cocoa developer, albeit a new one. So I have every right to
post this question on this site. Thank you very much, but clicking on
the application in the dock does not work in my case. That would be a
rather obvious answer and one of the many
Thanks to Nick and Pascal the issue is closed, successfully.
Jim
JIM ROGERS, W4ATK
w4...@bellsouth.net
http://web.me.com/jimrogers_w4atk
K3/100 P3
K2/10
JIM ROGERS
jimrogers_w4...@me.com
http://web.me.com/jimrogers_w4atk
___
Cocoa-dev mailing
Dear all,
I used to ask one question about NSCache. Actually, I need to build a view
like the 'Photos' application.
Now it works, but need to be improved: the speed of dragging, loading images
is not good enough.
Please give me some general ideas on how to load images on time and manage
the
On May 17, 2011, at 8:08 AM, Pascal J. Bourguignon wrote:
JAMES ROGERS jimrogers_w4...@me.com writes:
I am a cocoa developer, albeit a new one. So I have every right to
post this question on this site.
I think Joanna can be forgiven for an honest misunderstanding.
Thank you very much, but
On May 17, 2011, at 8:44 AM, Andy Lee wrote:
Also you can implement the applicationShouldHandleReopen:hasVisibleWindows:
method mentioned above to automatically reopen the window, if you prefer.
Though I'm not sure as a user I'd like that. Maybe that is what people meant
when they said that
I'm just beginning to learn about Cocoa-Touch programming, so it will be awhile.
Eventually, I would like to upload the intermediate stages of my iOS App to my
iPad just for testing. I am very familiar with the iOS software simulator, but
I would like to use my iPad as a test platform, the
On May 17, 2011, at 9:35 AM, John Love wrote:
Do I have to formally be a Apple Developer ($99 per year) to get my
pre-release iOS App onto my iPad?
Yes.
Finally, for every year I have my final iOS App in the App Store, do I have
to shell out $99.
Yes.
I don't know if this influences
Well give us something to go on at least! What did you use to build it? What
have tried so far in profiling/improving the performance?
On 17 May 2011, at 13:35, Leon Qiao wrote:
Dear all,
I used to ask one question about NSCache. Actually, I need to build a view
like the 'Photos'
I am a cocoa developer, albeit a new one. So I have every right to
post this question on this site.
I think Joanna can be forgiven for an honest misunderstanding.
My apologies; I also moderate other technical newsgroups and it is sometimes
easy to jump to the wrong conclusion, especially
Joanna,
No problem. I should have phrased it better.
After many exchanges the simplest and best solution for this particular
application came from Andy, just disable the button.
I am a retired Senior Systems Analyst and certainly can be guilty of tossing a
few stones at glass houses.
Picking
On May 17, 2011, at 1:26 AM, Bill Cheeseman wrote:
Answering my own question: Although it's hard to be sure that a random
problem is really fixed, it appears that the solution was to stop creating
Core Animation layers in the view's -initWithFrame: method and instead create
them in the
On 17.05.2011, at 14:54, Andy Lee wrote:
On May 17, 2011, at 8:44 AM, Andy Lee wrote:
Also you can implement the applicationShouldHandleReopen:hasVisibleWindows:
method mentioned above to automatically reopen the window, if you prefer.
Though I'm not sure as a user I'd like that. Maybe that
This is a classic instance of having to look at the nature or the application
to decide if it is an appropriate action.
I use both models depending upon the application. The general approach I take
is to look at the app in question determine if there is any legitimate reason
it should stay
On May 17, 2011, at 11:33 AM, David Duncan wrote:
There should be no actual restriction like that however. That said, as you
point out, if you have view that supports layers and come from a nib, you
often have to duplicate work to allow it to work in both situations.
I'm not sure I follow
Dear Bill,
You are right. Polling is not good.
But I noticed that Cocoa threading provides wait/pulse-like synchronization
techniques, such as Condition. I believe these techniques can be used to
control a thread which has a while-true loop. So I think RunLoop can be
replaced. Do you think so?
On May 17, 2011, at 9:49 AM, Bill Cheeseman wrote:
On May 17, 2011, at 11:33 AM, David Duncan wrote:
There should be no actual restriction like that however. That said, as you
point out, if you have view that supports layers and come from a nib, you
often have to duplicate work to allow
On May 17, 2011, at 9:54 AM, Bing Li wrote:
Dear Bill,
You are right. Polling is not good.
But I noticed that Cocoa threading provides wait/pulse-like synchronization
techniques, such as Condition. I believe these techniques can be used to
control a thread which has a while-true loop. So
The basic problem comes about when a view in the nib has wantsLayer=NO, but
the view itself always wants to be layer backed. If you setWantsLayer:YES
inside of -initWithFrame:, then by the time you get to -awakeFromNib
wantsLayer=NO again
Would there be any issue with overriding
On Tue, May 17, 2011 at 10:21 AM, Keith Duncan ke...@33software.com wrote:
The basic problem comes about when a view in the nib has wantsLayer=NO, but
the view itself always wants to be layer backed. If you setWantsLayer:YES
inside of -initWithFrame:, then by the time you get to
On Tue, May 17, 2011 at 8:56 AM, Andy 'Dru' Satori d...@druware.com wrote:
This is a classic instance of having to look at the nature or the application
to decide if it is an appropriate action.
I use both models depending upon the application. The general approach I
take is to look at the
I'm making an iPad-only view-based app. The large screen size of the iPad will
be split into 4 views, each operating independently, so the iPad is a perfect
fit.
However, in Interface Builder, the default xibs that are created with the
project appear to be iPhone-sized. How do I get IB to
Okay, fishing through the menus, I found Create iPad Version. Cool.
On May 17, 2011, at 10:48 AM, Nathan Sims wrote:
I'm making an iPad-only view-based app. The large screen size of the iPad
will be split into 4 views, each operating independently, so the iPad is a
perfect fit.
However,
On May 17, 2011, at 12:58 PM, David Duncan wrote:
The basic problem comes about when a view in the nib has wantsLayer=NO, but
the view itself always wants to be layer backed. If you setWantsLayer:YES
inside of -initWithFrame:, then by the time you get to -awakeFromNib
wantsLayer=NO again.
On Tue, May 17, 2011 at 11:35 AM, Bill Cheeseman wjcheese...@gmail.com wrote:
I agree that the explanation doesn't logically lead to a prohibition on
creating layers in -initWithFrame:. That's why I initially created them
there, deferring only the construction of the layer tree to
On 17 May 2011, at 9:54 AM, Bing Li wrote:
But I noticed that Cocoa threading provides wait/pulse-like synchronization
techniques, such as Condition. I believe these techniques can be used to
control a thread which has a while-true loop. So I think RunLoop can be
replaced. Do you think so?
With Xcode 3.2.6, I am getting the (well-discussed) error
The OutType type doesn't map to any NSDocumentClass.
after
theOutDoc = [[NSDocumentController sharedDocumentController]
makeUntitledDocumentOfType:@OutType error:outError];
I cannot see where I went wrong. My AppDelegate plist
On Tue, May 17, 2011 at 12:24 PM, McLaughlin, Michael P.
mp...@mitre.org wrote:
With Xcode 3.2.6, I am getting the (well-discussed) error
The OutType type doesn't map to any NSDocumentClass.
after
theOutDoc = [[NSDocumentController sharedDocumentController]
On May 17, 2011, at 2:58 PM, Kyle Sluder wrote:
You could also try using -makeBackingLayer. That's useful if your view
can be used both programmatically and in a nib.
I wonder if that method works for a layer-hosting view, which is what my view
is -- not a layer-backed view. But even if it
Hello.
UI have 2 UUIImageView which Im sliding in/out to display some images, but each
time the new image slides in the memory keeps growing and growing and growing
even I set to nil the image of the outgoing UIImageview.
This is what Im doing.
Please any help will be very appreciate it.
The App Store Review Guidelines state (2.16) that Multitasking apps
may only use background services for their intended purposes: VoIP,
audio playback, location, task completion, local notifications, etc.
There is a background mode plist key (UIBackgroundModes=voip) for
apps that provide VOIP
All,
I am building a library to be used by other apps. I have included the
json-framework in the library project and used the -ljson flag as directed. Now
this all works fine, until my app uses one of the JSON categories that the
library implements. if I add the json-framework to the app it
On May 17, 2011, at 1:28 PM, Gustavo Pizano wrote:
self.nextImageView.image = [UIImage imageNamed:[[images
objectAtIndex:indexActualImage]bigImageName]];
Images loaded with +imageNamed: are cached by your application. This cache
should respond to memory warnings, but until
On May 17, 2011, at 2:03 PM, Damien Cooke wrote:
I am building a library to be used by other apps. I have included the
json-framework in the library project and used the -ljson flag as directed.
Now this all works fine, until my app uses one of the JSON categories that
the library
On 17 May 2011, at 2:03 PM, Damien Cooke wrote:
I am building a library to be used by other apps. I have included the
json-framework in the library project and used the -ljson flag as directed.
Now this all works fine, until my app uses one of the JSON categories that
the library
On 17 May 2011, at 3:50 PM, Chris Markle wrote:
The App Store Review Guidelines state (2.16) that Multitasking apps
may only use background services for their intended purposes: VoIP,
audio playback, location, task completion, local notifications, etc.
There is a background mode plist key
All of this - and please file a bug report requesting a way for a background
app to have network keep alives (would be good for any app that needs to poll
or keep a connection). I've filed a bug report. You should too. That's how
Apple determines what's needed.
On May 17, 2011, at 5:07 PM,
On May 17, 2011, at 4:50 PM, Chris Markle wrote:
The App Store Review Guidelines state (2.16) that Multitasking apps
may only use background services for their intended purposes: VoIP,
audio playback, location, task completion, local notifications, etc.
Is anyone using this form of
Steve,
This is a psychological quiz, right? Let's see if someone, who managed to
violate
the guidelines and GET AWAY with it, will come on a public list and admit to
it.
Yeah I wondered about that... They could always reply directly to me -
I don't work for Apple. For a small fee I could
As far as I can tell, OverlayViews are not clickable.
So, I'm subclassing MKMapView and overloading the GestureRecognizers
actions handlers to deal with that.
Considering that these actions handlers are not documented (well, they
are through a quick NSLog output), would doing that be considered
This seems like it should be such a fundamentally obvious difference,
but I've been quite puzzled about it ever since I first started
working with Cocoa: when is it more appropriate to call -[NSWindow
orderOut:] than -[NSWindow performClose:] (or just plain -close)?
At first glance, it appears
Hi Kyle.
I don't believe there's a distinction here between high level and low level
API. Iit's just a simple distinction between being done with the window and not
being done with the window. When your app is permanently done with a window and
will never display it again, you call -close,
On Tue, May 17, 2011 at 5:55 PM, Jeff Johnson
publicpost...@lapcatsoftware.com wrote:
I believe that the main purpose not only of -isReleasedWhenClosed but also
NSWindowWillCloseNotification is to handle memory management and/or clean up
when you're permanently done with a window. Indeed, the
Hi all,
I'm trying to use CATransition in my app to provide an animated slide
transition when swapping views. I don't want to permanently layer back my views
because they cause various glitches (no subpixel antialiasing, resize issues
when backed with a CATiledLayer, etc.) To get around this,
So I'm trying to develop an app that runs as an NSStatusItem, but it keeps
bringing itself to the foreground whenever a window belonging to it is
left-clicked on. And that's no good. I want it to stay in the background
at all times -no matter what-(which has to be possible because
Accessibility
I'm developing a barcode scanner application, specifically for the
iPhone/iPod Touch. I'm using the ZXing open source library in conjunction
with AVCaptureVideoDataOutput and sampleBufferDelegate to decode QRCodes
from the video camera.
I'm trying to reduce the frame rate to the
On May 17, 2011, at 10:15 AM, banned_acco...@lavabit.com wrote:
There's probably
a simple solution to all of this. But I can't find it. Help?
NSNonactivatingPanelMask?
--
Scott Ribe
scott_r...@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice
Solved.
Saving the original gesture recognizers and replacing them with other
ones works well.
On Tue, May 17, 2011 at 5:10 PM, Stephane Sudre dev.iceb...@gmail.com wrote:
As far as I can tell, OverlayViews are not clickable.
So, I'm subclassing MKMapView and overloading the
52 matches
Mail list logo
