On Feb 5, 2013, at 6:53 PM, Graham Cox wrote:
> So, the question is how can I tap into the dragging session loop to do the
> autoscroll?
Typically one calls +startPeriodicEvents… in -draggingEntered:, and calls
+stopPeriodicEvents in -draggingExited:.
--Kyle Sluder
_
Ok, that's correct. I can see NSMultipleValues in some of my detail views. In a
couple of other cases it is working, but not in one particular case. Its
default behaviour correct? I knew that all my monkeying was indicative that I
was doing something wrong.
On Feb 5, 2013, at 8:01 PM, Graham C
On 06/02/2013, at 2:08 PM, livinginlosange...@mac.com wrote:
> Now users can edit an item 2 ways. They can tab into the control (in this
> case an NSTextField or an NSComboBox) or mouseDown: into the control. I want
> to basically interpose both ways of accessing a control. The minute they try
I am revisiting an issue with which I had a problem earlier. I have a
detail view which is bound to my model in an NSArrayController. Currently, I
can edit multiple selections. What I want to accomplish is warn my users when
they are about to edit multiple items and give them the choice
On 06/02/2013, at 12:31 PM, Kyle Sluder wrote:
> On Tue, Feb 5, 2013, at 03:39 PM, Graham Cox wrote:
>> I need to autoscroll my view when I'm handling -draggingUpdated: but
>> -autoscroll: takes an NSEvent and I don't have one. I thought I could use
>> [myWindow currentEvent] but that doesn't se
On Tue, Feb 5, 2013, at 03:39 PM, Graham Cox wrote:
> I need to autoscroll my view when I'm handling -draggingUpdated: but
> -autoscroll: takes an NSEvent and I don't have one. I thought I could use
> [myWindow currentEvent] but that doesn't seem correct for the dragging
> session.
Why not? If you
On Feb 5, 2013, at 19:09:54, Lee Ann Rucker wrote:
> There's probably a KVO observer on isDocumentEdited; if nothing triggers
> setDocumentEdited then it doesn't know to check it.
>
> updateChangeCount: says
>
> If you are implementing undo and redo in an application, you should increment
> t
At 8:13 AM -0800 2/5/13, Glenn L. Austin wrote:
I understand the *reasoning* behind
performSelector:withObject:afterDelay:, but I've banned that from
code I work on.
In the OP's case, I think he just needs to perform the selector
asynchronously so he doesn't deadlock -- waitUntilDone:NO ought
On Feb 5, 2013, at 3:08 PM, Steve Mills wrote:
> On Feb 5, 2013, at 15:12:43, Markus Spoettl wrote:
>
>> I don't think it's meant to be overridden that way because the framework
>> doesn't realize that the state has changed. You should probably call
>> -setDocumentEdited: instead, or, as an a
I have a custom view on which I place multiple NSTextViews, but when printed
only the *content* last NSTextView placed actually shows up. That is, to make
sure I am placing view appropriately my NSTextView subclass draws a box around
its bounds. The box shows up, but no text inside even though I
Hello,
I am trying to take a CVImageBufferRef received from the following video
capture callback:
- (void)outputVideoFrame:(CVImageBufferRef)videoFrame
withSampleBuffer:(QTSampleBuffer *)sampleBuffer
fromConnection:(QTCaptureConnection *)connection
...and feed to to an FFmpeg codec for furthe
This should be a simple one...
I need to autoscroll my view when I'm handling -draggingUpdated: but
-autoscroll: takes an NSEvent and I don't have one. I thought I could use
[myWindow currentEvent] but that doesn't seem correct for the dragging session.
How should this be handled?
--Graham
On 06/02/2013, at 10:08 AM, Steve Mills wrote:
> From the docs for setDocumentEdited:
You need to use [NSDocument updateChangeCount:(NSDocumentChangeType)
changeType];
--Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please
On Feb 5, 2013, at 15:12:43, Markus Spoettl wrote:
> I don't think it's meant to be overridden that way because the framework
> doesn't realize that the state has changed. You should probably call
> -setDocumentEdited: instead, or, as an alternative, implement undo and use an
> NSUndoManager w
OK. Thanks for the quick and definitive reply. I'll file a bug report on the
CALayer class reference - it is a bit misleading.
Dave
On 2013-02-05, at 3:55 PM, David Duncan wrote:
> On Feb 5, 2013, at 12:29 PM, Dave Fernandes
> wrote:
>
>> My understanding is that CALayer's filters property
On 2/5/13 9:59 PM, Steve Mills wrote:
Do I need to do anything to force the close box to update its status from non
dirty to dirty? Our document subclass overrides isDocumentEdited and is
returning true, yet the close box appears clean. If I Close, isDocumentEdited
again returns true and the save
Do I need to do anything to force the close box to update its status from non
dirty to dirty? Our document subclass overrides isDocumentEdited and is
returning true, yet the close box appears clean. If I Close, isDocumentEdited
again returns true and the save dlog appears. If I create a new wind
On Feb 5, 2013, at 12:29 PM, Dave Fernandes wrote:
> My understanding is that CALayer's filters property should work on iOS 6.
Unfortunately this is incorrect. The filter properties on CALayer do not work,
which is why you don't get the bloom effect.
For the record, on OS X where they do work
I'm trying to apply a bloom effect to shapes drawn in a CALayer subclass
(drawInContext: method). This is on iOS 6 in the simulator. The CIBloom filter
is created, but it doesn't seem to affect the layer's rendering. My
understanding is that CALayer's filters property should work on iOS 6. But
> Does your crash log show multiple threads? I would expect that the crash log
> shows only one thread because NSTask called fork() already.
Hmm. Yes, there's only one thread. I didn't notice that. That explains the
crash (of the forked process) "instead of an exception," like you mentioned.
>
On Feb 4, 2013, at 8:58 AM, Kyle Sluder wrote:
> On Sun, Feb 3, 2013, at 11:58 PM, 尹佳冀 wrote:
>> Thanks Mike seem You are right, and I write like this
>>
>> [self performSelector:@selector(doTheThing) withObject:nil
>> afterDelay:0.5];
>> it can work correctly.
>
> Magic constants like this ar
On 5 Feb 2013, at 10:38, Thomas Zoechling wrote:
>
> Thanks for your response,
>> Given the right conditions, NSFileWrapper can make writing vastly more
>> efficient by writing hard links for unchanged files, rather than recreating
>> them afresh. Have you determined whether this is happening
On Feb 4, 2013, at 11:26 AM, Seth Willits wrote:
> Exception Type: EXC_BREAKPOINT (SIGTRAP)
> Exception Codes: 0x0002, 0x
>
> *** NSTask: Task create for path
> '/Applications/App.app/Contents/Resources/mytask' failed: 22, "Invalid
> argument". Terminating temporary
Thanks for your response,
> Given the right conditions, NSFileWrapper can make writing vastly more
> efficient by writing hard links for unchanged files, rather than recreating
> them afresh. Have you determined whether this is happening at all?
Currently I am trying to figure out what those con
24 matches
Mail list logo