On Jul 27, 2012, at 10:36 AM, Curt Clifton wrote:
> On Jul 27, 2012, at 8:55 AM, Nick Zitzmann wrote:
>
>> But I need to be able to see **all** invocations of the method from **all**
>> NSViews to catch the culprit, because I have a rather complicated view
>> hierarchy, including some views
On Mon, Aug 6, 2012, at 05:34 PM, Dave Keck wrote:
> > But Mike is still right; you're probably better served by using
> > -performSelectorOnMainThread::: rather than waking the run loop up yourself.
>
> I tend to disagree -- invoking CFRunLoopPerformBlock() and
> CFRunLoopWakeUp() is likely more
> But Mike is still right; you're probably better served by using
> -performSelectorOnMainThread::: rather than waking the run loop up yourself.
I tend to disagree -- invoking CFRunLoopPerformBlock() and
CFRunLoopWakeUp() is likely more performant since they're at the CF
level (which -performSele
On Aug 6, 2012, at 16:11 , Laurent Daudelin wrote:
> I found the problem after poking some more in Google. It is apparently a bug
> in UIKit. To fix it, I created a strong property in my controller connected
> to the UIGestureRecognizer and now, no more crash! So, the gesture
> recognizer, if
On 07/08/2012, at 9:11 AM, Laurent Daudelin wrote:
> So, the gesture recognizer, if nobody retains it, will be released without
> telling anyone, causing a random crash.
Doesn't that apply to any object? That's normal.
--Graham
___
Cocoa-dev mai
On 07/08/2012, at 9:12 AM, Lee Ann Rucker wrote:
> You could use an NSColorList, or take a cue from NSImage and have an [NSColor
> colorNamed:]
I have both of these; the 'named' methods are really just an additional
convenience. I'm not actually making use of them at present, so I've just ad
On Aug 6, 2012, at 3:38 PM, Graham Cox wrote:
>
> On 07/08/2012, at 2:38 AM, Kevin Perry wrote:
>
>> A stab in the dark: Have you tried running with OBJC_PRINT_REPLACED_METHODS
>> set? There's a small chance that you have code in your app or a library that
>> you're linking that replaces via
I found the problem after poking some more in Google. It is apparently a bug in
UIKit. To fix it, I created a strong property in my controller connected to the
UIGestureRecognizer and now, no more crash! So, the gesture recognizer, if
nobody retains it, will be released without telling anyone, c
On Aug 6, 2012, at 15:36 , Flavio Donadio wrote:
> Luca,
>
> The direction is where the swipe ends. UISwipeGestureRecognizerDirectionRight
> is for left-to-right.
>
> Cheers,
> Flavio
>
> On 06/08/2012, at 16:00, cocoa-dev-requ...@lists.apple.com wrote:
>
>> Hi All.
>> Probably my problem is
Yeah, that's the problem, the backtrace doesn't show any code related to my
gesture recognizers. But as soon as I delete it from my storyboard, the problem
vanishes. I've done it 3 times now so I'm pretty sure the gesture recognizers
is somehow causing a random crash.
-Laurent.
--
Laurent Daud
Hell Quincey.
So, how are you supposed to use those IB UIGestureRecognizers in IB? I haven't
seen any example that shows how to use them. Even the ScrollSuite sample
"TapToZoom" doesn't use them but build them programmatically. I mean, I don't
mind coding them but I thought I'd rather use them
On 07/08/2012, at 2:38 AM, Kevin Perry wrote:
> A stab in the dark: Have you tried running with OBJC_PRINT_REPLACED_METHODS
> set? There's a small chance that you have code in your app or a library that
> you're linking that replaces via category a method implementation internal to
> AppKit t
Luca,
The direction is where the swipe ends. UISwipeGestureRecognizerDirectionRight
is for left-to-right.
Cheers,
Flavio
On 06/08/2012, at 16:00, cocoa-dev-requ...@lists.apple.com wrote:
> Hi All.
> Probably my problem is very stupid with a very immediate answer, but I'm very
> new using st
On Aug 6, 2012, at 14:54 , Laurent Daudelin wrote:
> Forgot to mention that I also tried to connect the gestureRecognizers outlet
> of the UIImageView to the gesture recognizer, making sure the one from the
> scrollview had been removed with same result….
a. The backtrace you posted doesn't pr
Forgot to mention that I also tried to connect the gestureRecognizers outlet of
the UIImageView to the gesture recognizer, making sure the one from the
scrollview had been removed with same result….
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin
h
Hello.
I found a few examples of creating UIGestureRecognizer programmatically but
since they're in IB now, I thought why not using them there. So, I have an
Xcode 4.4 iOS 5.1 project using ARC with a UITableViewCell that contains a
UIScrollView, among other things, which scrollview contains an
On 6 Aug 2012, at 3:05 AM, Luca Ciciriello wrote:
> I'm trying to set a specific font in my UITextView.
>
> The font is Chalkboard SE Regular and my code is
>
> [[self textView] setFont:[UIFont fontWithName:@"Chalkboard se regular"
> size:39.0f]];
>
> but nothing appear un my UITextView.
>
Thanks, You are right. My problem was in the name of the font
(@"ChalkboardSE-Regular")
Luca.
On Aug 6, 2012, at 7:30 PM, Jens Alfke wrote:
>
> On Aug 6, 2012, at 1:05 AM, Luca Ciciriello
> wrote:
>
>> [[self textView] setFont:[UIFont fontWithName:@"Chalkboard se regular"
>> size:39.0f]]
On Aug 6, 2012, at 1:05 AM, Luca Ciciriello wrote:
> [[self textView] setFont:[UIFont fontWithName:@"Chalkboard se regular"
> size:39.0f]];
Make sure that UIFont call isn't returning nil. In my experience, APIs that
look up fonts by name are very picky about the name (for instance, you
lower
Hi All.
Probably my problem is very stupid with a very immediate answer, but I'm very
new using storyboard.
I've have 2 pages. in the first page I've the following code:
@property(strong, nonatomic) IBOutlet UISwipeGestureRecognizer
*swipeGestureNext;
1) swipeGestureNext = [[UISwipeGestureRec
A stab in the dark: Have you tried running with OBJC_PRINT_REPLACED_METHODS
set? There's a small chance that you have code in your app or a library that
you're linking that replaces via category a method implementation internal to
AppKit that +underPageBackgroundColor relies on.
Also, it might
On Aug 3, 2012, at 6:21 AM, Graham Cox wrote:
> On 03/08/2012, at 2:14 PM, Andreas Mayer wrote:
>> Am 03.08.2012 um 03:41 schrieb Graham Cox :
>>
>>> Has anyone else experienced issues with the Color Panel not showing in
>>> Mountain Lion?
>>
>> Working fine here.
>
> Working fine here too...
On Aug 6, 2012, at 2:44 AM, Dave Keck wrote:
>> Right, so what you actually want to do is change how you’re messaging the
>> main thread. Use something like
>> -performSelectorOnMainThread:withObject:waitUntilDone:modes: so you can
>> specify NSDefaultRunLoopMode and NSScrollEventCoallescing.
I have a spotlight importer that works just fine when I run mdimport from the
command line, but it fails with a sig11 when it runs automatically.
I've tested it on two machines under 10.7 and 10.8, with the same results.
Can anyone give any tips on how to debug this situation?
Thanks
Gideon
Hi All,
Presently I am working on authoring a PKG bundle for our application.
When a default PKG is deployed in UI workflow, the various default
screens are shown, even if I configure the PKG in PackageMaker for
minimal interaction (Welcome, Install location, summary screen,...).
My application is
> Right, so what you actually want to do is change how you’re messaging the
> main thread. Use something like
> -performSelectorOnMainThread:withObject:waitUntilDone:modes: so you can
> specify NSDefaultRunLoopMode and NSScrollEventCoallescing.
NSScrollEventCoallescing is a private run loop mod
On 5 Aug 2012, at 03:00, Dave Keck wrote:
>> I'm unsure of the wisdom of this approach. Presumably the scroll view is
>> intentionally blocking the runloop, and thus assuming that the runloop will
>> not fire its event sources until after the scrolling is complete. By waking
>> up the runloop,
Hi All.
I'm trying to set a specific font in my UITextView.
The font is Chalkboard SE Regular and my code is
[[self textView] setFont:[UIFont fontWithName:@"Chalkboard se regular"
size:39.0f]];
but nothing appear un my UITextView.
Where is my mistake?
Luca.
__
28 matches
Mail list logo
