On 17 Mar 2012, at 05:56, Prime Coderama wrote:
> Shouldn't the the SMJobBless example be used? Although I am still struggling
> to get this to work - even have an open Apple support issue.
>
I just build SMJobBless. Didn't work.
Then I changed "Joe Developer" with some iPhone Provisioning cer
On Mar 17, 2012, at 1:40 PM, G S wrote:
>
> By the way: I keep track of the view loaded/unloaded state with a flag in the
> view controller (which I toggle in viewDidLoad & viewDidUnload). Is this a
> typical strategy? This ensures that the controller's routines don't try to
> interact with
On Fri, Mar 16, 2012 at 9:45 PM, Roland King wrote:
> I think chances are you are still somehow calling a method on a view
> controller or similar which has been evicted.
>
I took a hard look at the two underlying controllers to make sure that they
are not referring to controls when the views ar
I think chances are you are still somehow calling a method on a view controller
or similar which has been evicted. Why that's the case with UIActionSheet and
not something else, I can't say. I was pretty careful in my project to ensure I
called methods only on view controllers with loaded views
I think this may all have changed a bit around iOS 5 when storyboards were
introduced. IIRC before that your main NIB file had the delegate in it (which
you hooked up to the delegate of the UIApplication). As you had different NIBs
for iPhone and iPad, you could have two delegates, so they did.
On Fri, Mar 16, 2012 at 7:53 PM, Roland King wrote:
> You've sure had a lot of problems with this!
>
Yeah, this is ridiculous. Researching it, I found that Instagram had the
same white-screen problem for a while. Unfortunately, I've found no way to
contact them.
There's clearly something wron
I see that I can select Universal for all project types. I guess what I
expected was two app delegates and a folder structure for iPad and iPhone.
Again I am just going off of tutorials etc that I found online.
I do recall reading that you needed to choose a windows based app because that
wa
You've sure had a lot of problems with this!
I just wrote a simple test app which has a Navigation Controller with Root, One
and Two screens. Root has a 'one' button which transitions to One, One has a
'Two' button which transitions to 2, all pushes. Root and One both have
'Action' buttons whi
Thanks for asking this, Brian. I've wondered the same thing, and in fact I
went through my code and removed almost all property declarations from my
view controllers. Since most properties are declared as "retain", you're
just increasing your bookkeeping to avoid leaks. Not to mention the sheer
I gave that session. At let me sate for the record, now, that exactly when drag
starts is UNDEFINED. Obviously, it will start soon!
I've been in your shoes before (different company). I've had to make
cross-platform code work with asynchronous OS X API where other platforms had
synchronous API.
This is an interesting discussion, but there is a lot of misunderstanding of
the concept of information hiding if not in what has been said here, but
generally in the industry. This term was introduced by David Parnas, and I
think it is a bit unfortunate because if you read his papers on this he
Sorry to be late to this party. I've been busy. ;)
The "System" doesn't know if momentum scroll events will follow normal scroll
event phrase or not. There is no way for the underlying driver to inform the
system of this. Sorry. I have to deal with this problem inside appkit as well.
It gets ev
A few points worth clarifying for the original poster here ...
Using a @property does NOT actually expose the underlying implementation.
@properties are like configurable ACCESSORS ... they do *NOT* necessarily
provide direct access to the implementation. You can implement them however
you want. Y
I'm don't want to give details here as it is off topic. But I can give you some
hints.
To use task_for_pid, you don't need to run your tool as root.
You can to it by properly signing your tool with a trusted certificate (a self
signed certificate is enough as long as you install it properly in y
On Mar 16, 2012, at 6:53 PM, cocoa-dev-requ...@lists.apple.com wrote:
> Date: Fri, 16 Mar 2012 15:53:30 -0700
> From: Jens Alfke
> To: Eeyore
> Cc: cocoa-dev list
> Subject: Re: Why so many public properties all up in my grizzle?
> Message-ID: <4aba472f-cdad-47f3-8544-a5538f5ac...@mooseyard.co
Shouldn't the the SMJobBless example be used? Although I am still struggling to
get this to work - even have an open Apple support issue.
On 16/03/2012, at 11:45 PM, Jean-Daniel Dupas wrote:
>
> Le 16 mars 2012 à 13:27, Gerriet M. Denkmann a écrit :
>
>>
>> On 16 Mar 2012, at 19:17, Jean-Dani
On Mar 16, 2012, at 2:57 PM, Eeyore wrote:
> So simply hiding the actions in the implementation doesn't protect you from
> finding out the method's name and calling it.
Well, sure. If you’re in the same process, there’s nothing protecting you from
malicious code. The same goes for C++ or assem
David Duncan indicates that some of this can be alleviated with newer runtimes,
but Objective C's messaging system allows you to send messages to objects even
if those messages are not declared in the object's interface. So simply hiding
the actions in the implementation doesn't protect you from
On 3/16/12 2:00 PM, Brian Lambert wrote:
> This means that my UILabel called labelMyLabel is publicly available.
> Anyone who has access to an instance of MyViewController can do anything
> they want to with my label, including replacing it.
>
> Also, anyone who has an instance of MyViewController
On 16.03.12 21:48, Seth Willits wrote:
Perhaps there's a better time to do cleanup altogether?
I'm hoping there is one, I'm not happy with the way its working
right now. Thanks anyway!
Well you could spitball about why you need post-scroll clean up.
Maybe there's a way to eliminate it.
The
> That time has passed now, so you can now completely specify IBOutlets (and
> IBActions) in your implementation file and hide the details from the outside
> world. If you want properties, you can use a class extension like so to add
> them:
Sorry to hijack this conversation, but I've been mean
Please don't crosspost. Choose one list.
--Kyle Sluder
___
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/Unsub
On Mar 16, 2012, at 2:00 PM, Brian Lambert wrote:
>
> To me, this is how things should be. The implementation details of how my
> view works are hidden.
>
> Am I missing something?
Part of the problem was that prior to Xcode 4, IBOutlets needed to be declared
in the header, or Interface Build
I’ve been developing iOS applications full-time for about 6 months now and
I love it. I feel pretty strong on the platform now.
I have a lingering question about something that’s really been bugging the
heck out of me, though, that I thought I would ask the list and get some
feedback on.
It seems
On Mar 16, 2012, at 1:38 PM, Markus Spoettl wrote:
> What I'm doing now is using -performSelector:withObject:afterDelay: with a
> delay of about 0.1 seconds.
Yeah, that's all I could figure doing.
>> Perhaps there's a better time to do cleanup altogether?
>
> I'm hoping there is one, I'm not
On 16.03.12 20:29, Seth Willits wrote:
Can you dispatch_async(main_queue, ^{ if (did not start momentum)
cleanUp(); }); to insert that after the next handling of the event
loop which should either start the momentum cycle or not (if it isn't
needed)? I don't know if that cycle is guaranteed to
On Mar 16, 2012, at 11:38 AM, Markus Spoettl wrote:
> I take it either (a) I'm the only one here having this problem or (b) it is
> so badly explained that no one knows that I'm talking about? If it's (b) I
> can try again...
Never needed to do it.
Can you dispatch_async(main_queue, ^{ if (
On Mar 15, 2012, at 11:53 PM, Peter Zegelin wrote:
> I need to implement something akin to the iTunes Fast Forward or Rewind
> buttons, where a quick mouse click has a different action to when the button
> is pressed for a longer time. I also need to link this action to a short or
> long press
On Mar 16, 2012, at 7:54 AM, Shawn Bakhtiar wrote:
> Ok so now I'm thoroughly confused.
You added them as subviews when you started:
[[[wc window] contentView] addSubview:graph1View];
[[[wc window] contentView] addSubview:msds2View];
[[[wc window] contentView] addSubview:msds1View];
Hello,
I take it either (a) I'm the only one here having this problem or (b)
it is so badly explained that no one knows that I'm talking about? If
it's (b) I can try again...
Regards
Markus
On 11.03.12 20:43, Markus Spoettl wrote:
Hello,
in a custom view I'm processing -scrollWheel: even
> Subject: Re: NSViewAnimation fade[In/Out]effect not working
> From: sli...@araelium.com
> Date: Thu, 15 Mar 2012 20:09:25 -0700
> To: cocoa-dev@lists.apple.com
>
> On Mar 15, 2012, at 7:49 PM, Shawn Bakhtiar wrote:
>
> > I am trying to fade in and out 4 different views based on the user clic
More:
UIControlEventTouchDownRepeat
A repeated touch-down event in the control; for this event the value of the
UITouch tapCount method is greater than one.
On Mar 16, 2012, at 9:57 AM, Alex Zavatone wrote:
> Pardon me if I'm only using iOS terms.
>
> OK. First off, your UIButton needs to
Pardon me if I'm only using iOS terms.
OK. First off, your UIButton needs to respond to UIControlEventTouchUpInside
and also needs to respond to UIControlEventTouchDownRepeat.
Check out the UIControl Class Reference for the nature of the Touch Events you
can respond to.
You'll need a timer
Le 16 mars 2012 à 13:27, Gerriet M. Denkmann a écrit :
>
> On 16 Mar 2012, at 19:17, Jean-Daniel Dupas wrote:
>
>>
>> Le 16 mars 2012 à 12:33, Gerriet M. Denkmann a écrit :
>>
>>> I have an app which needs to do (among other things) to call task_for_pid()
>>> which seems to work only for roo
On 16 Mar 2012, at 19:17, Jean-Daniel Dupas wrote:
>
> Le 16 mars 2012 à 12:33, Gerriet M. Denkmann a écrit :
>
>> I have an app which needs to do (among other things) to call task_for_pid()
>> which seems to work only for root.
>>
>> The modern way to do this is have a small companion tool
Le 16 mars 2012 à 12:33, Gerriet M. Denkmann a écrit :
> I have an app which needs to do (among other things) to call task_for_pid()
> which seems to work only for root.
>
> The modern way to do this is have a small companion tool which exchanges
> info with my app via XPC. Correct?
>
> I am
I have an app which needs to do (among other things) to call task_for_pid()
which seems to work only for root.
The modern way to do this is have a small companion tool which exchanges info
with my app via XPC. Correct?
I am also thinking about sandboxing (just as a learning experience). Or is
I checked all 7 iOS project types when I wrote the reply and they all support
iPhone, iPad and Universal in 4.3.1.
On Mar 16, 2012, at 6:22 PM, Eric Dolecki wrote:
> There is only one project type now that supports universal if I remember
> correctly. Just make sure to pick the correct one.
>
There is only one project type now that supports universal if I remember
correctly. Just make sure to pick the correct one.
Sent by Eric's faithful iPad.
On Mar 16, 2012, at 1:39 AM, Roland King wrote:
> Works fine for me. Are you sure, on the first screen after you picked
> application type
The situation is pretty simple: a view controller at the top of our
navigation controller's stack presents a modal view controller.
When the user's done with the modal view, he makes one of several choices
that call the modal controller's delegate and cause the delegate to dismiss
the modal view.
Hi,
I was wondering if it might be possible to implement an NSRuleEditor with
variable-height rows. There is a "rowHeight" property that can be set, but that
sets the same height for all rows. I can override it with a subclass, but I
don't see any obvious way to know which row height is being r
41 matches
Mail list logo
