On 28/06/2012, at 4:30 PM, Richard Altenburg (Brainchild) wrote:
> You should watch "Session 231 - What's New with Gestures" from the WWDC 2012
> video sessions...
I did, but I have to target 10.6.x and later. Sorry I forget to mention that.
BTW, features that are part of M Li.. are still
The NDA is why I only gave you the title of the video, all developers in this
list can access the WWDC videos and see for themselves what is new.
I guess for 10.6 and 10.7 you could roll your own "Smart Zoom" functionality,
but that is probably not what you wanted to hear.
[[[Brainchild alloc]
On 28/06/2012, at 5:06 PM, Richard Altenburg (Brainchild) wrote:
> I guess for 10.6 and 10.7 you could roll your own "Smart Zoom" functionality,
> but that is probably not what you wanted to hear.
>
>
Yes, it is what I wanted to hear, or more precisely, some sort of pointer or
"how to" abou
On Jun 28, 2012, at 00:14 , Graham Cox wrote:
> Specifically, the problem is that the -clickCount property of an NSEvent is
> only applicable to mouse events, not touch events. So what's the right way to
> trap this specific gesture? I have read the various touch-input documentation
> but nothi
Hi,
Got a view-based table view and instead of using reloadData I'm removing the
existing rows and inserting the new rows so that I can have animation. I'm
also resizing the window in-between these 2 steps because my window resizes to
fit how many rows are in my table view. This works great w
Point well taken. As it turns out all issues were related to Xcode.
-koko
On Jun 27, 2012, at 2:03 PM, Kyle Sluder wrote:
> On Jun 27, 2012, at 12:53 PM, koko wrote:
>
>> Ok, so what is the real truth regarding using a base SDK of 10.6 and a
>> deployment target of 10.5?
>>
>> The blogospher
On Jun 27, 2012, at 2:53 PM, koko wrote:
> Ok, so what is the real truth regarding using a base SDK of 10.6 and a
> deployment target of 10.5?
>
> The blogosphere says this cannot be done and Apple says it is OK.
>
> We have issues running a 10.6 SDK build on a 10.5.8 system.
>
> We have a cer
Hi everybody,
I’m trying to add a transparent editable NSTextField to a view. As long as the
field is not editable (e.g. a label), everything is fine; but with an editable
field, I get a background fill. I imagine this is under the window NSTextView
responsibility. Has someone already succeeded
Whenever you support an earlier OS, you should always have that earliest and
all intermediate SDKs available, and you should make it a standard practice to
build your products against those SDKs at least before releasing to customers
just as you do an analyzer build. This will help you identify
Hello,
I'm writing an application that handles results for a running club.
I have an NSTableView that has columns bound to a CoreData Entity such as
Entries.arrangedObjects.position, position is an NSString that contains numbers
such as @"1" and @"2" or @"" but the position can also be @"DNF" (
On 28 Jun 2012, at 10:22 AM, Vincent Habchi wrote:
> I’m trying to add a transparent editable NSTextField to a view. As long as
> the field is not editable (e.g. a label), everything is fine; but with an
> editable field, I get a background fill. I imagine this is under the window
> NSTextView
> My next step (which is my way of saying I haven't tried it) would be to
> investigate -[ windowWillReturnFieldEditor:toObject:], and
> set the field editor's backgroundColor (it's in NSText) to the transparent
> color.
I'll do that, yes. Besides, I need to override the cursor to make it look
In IB you can set the "Draws Background" property to no (uncheck the box) or
send the NSTextField a SetDrawsBackground: NO message.
On Jun 28, 2012, at 11:22 AM, Vincent Habchi wrote:
> Hi everybody,
>
> I’m trying to add a transparent editable NSTextField to a view. As long as
> the field is
Le 28 juin 2012 à 18:30, Charlie Dickman <3tothe...@comcast.net> a écrit :
> In IB you can set the "Draws Background" property to no (uncheck the box) or
> send the NSTextField a SetDrawsBackground: NO message.
Yep, but that’s working only for non-editable fields. In an editable field, I
get a
On 2012 Jun 27, at 22:42, Quincey Morris wrote:
> the setter should only contain the second part ("Set ivar, needsDisplay").
>
> It seems to me this should prevent selection changes from rebounding onto the
> data model.
Yes.
> Using mouseDown kinda feels wrong to me. Wouldn't it make more se
On Jun 28, 2012, at 10:49 , Jerry Krinock wrote:
> OK, but effectively this means that I simply factor this -changeRating:
> action method out of my -mouseDown: method. Only -mouseDown: will invoke
> -changeRating: at this time.
>
> I don't think I've ever seen a control class implementing an
Hi Vincent,
Have you tried setDrawsBackground:NO on your NSTextField?
Below was what I used.
I don't know if any of the other instance variables I set are important for
your case but they might be.
HTH,
Joel
- (void) initTextField;
{
[self setBordered:NO];
[self setFocusRingType:NSFocusR
I have an application which I am trying to update to use the new pasteboard
protocols, NSDragSession, etc. The new version requires Lion. Drag/drop
has been an absolute nightmare. The main windows have to handle a large
number of drop types, plus there is a separate library with its own coredata
On Jun 28, 2012, at 4:30 AM, Rick C. wrote:
> Hi,
>
> Got a view-based table view and instead of using reloadData I'm removing the
> existing rows and inserting the new rows so that I can have animation. I'm
> also resizing the window in-between these 2 steps because my window resizes
> to
On 6/28/12, Gary L. Wade wrote:
> Whenever you support an earlier OS, you should always have that earliest and
> all intermediate SDKs available, and you should make it a standard practice
> to build your products against those SDKs at least before releasing to
> customers just as you do an analyz
On Jun 28, 2012, at 1:58 PM, Eric Wing wrote:
>
> One additional gotcha that I have hit multiple times is that if your
> application links to system .dylibs (not .frameworks), Xcode links to
> the explicit filename versioned .dylib file on your system that the
> generic one is symlinked to. This
On 6/28/12, Kyle Sluder wrote:
> On Jun 28, 2012, at 1:58 PM, Eric Wing wrote:
>
>>
>> One additional gotcha that I have hit multiple times is that if your
>> application links to system .dylibs (not .frameworks), Xcode links to
>> the explicit filename versioned .dylib file on your system that t
On Jun 28, 2012, at 1:16 PM, Robert Tillyard wrote:
> Hello, Keary,
>
> Thank you for your reply.
>
> Would the selector in the model be in the class for the CoreData Entity or os
> it in the WindowController sub-class that controls the window that the
> TableView is in?
>
> Would you know w
On 2012 Jun 28, at 11:04, Quincey Morris wrote:
> I'm not sure now why your control needs a 'rating' ivar. Doesn't this just
> duplicate the value of the control's objectValue, and create extra
> housekeeping?
In this situation, probably yes, but it is quite normal for Cocoa controls to
have
Great I will check this out thanks Corbin!
rc
On Jun 29, 2012, at 4:26 AM, Corbin Dunn wrote:
>
> On Jun 28, 2012, at 4:30 AM, Rick C. wrote:
>
>> Hi,
>>
>> Got a view-based table view and instead of using reloadData I'm removing the
>> existing rows and inserting the new rows so that I c
On 28/06/2012, at 5:31 PM, Quincey Morris wrote:
> On Jun 28, 2012, at 00:14 , Graham Cox wrote:
>
>> Specifically, the problem is that the -clickCount property of an NSEvent is
>> only applicable to mouse events, not touch events. So what's the right way
>> to trap this specific gesture? I ha
On Jun 28, 2012, at 19:57 , Graham Cox wrote:
> - (void) touchesBeganWithEvent:(NSEvent*) event
> {
> NSSet* touches = [event touchesMatchingPhase:NSTouchPhaseBegan
> inView:self.view];
>
> if([touches count] == 2 )
Well, this looks wrong to me. In general, each of the 2
On 29/06/2012, at 1:17 PM, Quincey Morris wrote:
> Well, this looks wrong to me. In general, each of the 2 touches is going to
> begin at a different time, which means this method will be called twice, and
> there's only be one touch in the set at each call. (The touch that began
> earlier is
On 29/06/2012, at 1:17 PM, Quincey Morris wrote:
>> NSSet* touches = [event touchesMatchingPhase:NSTouchPhaseBegan
>> inView:self.view];
Ah, noticed a silly mistake. If I use NSTouchPhaseTouches here, I get a count
of 2 far more often. That suggests that in fact events are coalesced, or at
l
Unfortunately Corbin I'm not sure I'm following here. So I remove my old rows
sliding left and then resize my window and at that point I currently have no
rows (my datasource has been updated though). So if I try to call
rowViewAtRow: I get an exception since I have no rows. I can go ahead an
On Jun 28, 2012, at 4:19 PM, Kyle Sluder wrote:
> On Jun 28, 2012, at 1:58 PM, Eric Wing wrote:
>
>>
>> One additional gotcha that I have hit multiple times is that if your
>> application links to system .dylibs (not .frameworks), Xcode links to
>> the explicit filename versioned .dylib file on
31 matches
Mail list logo
