On Wednesday, 24. April 2013 at 1:28, Ken Thomases wrote:
Hi Ken,
> It's not clear if you tried to use [self invalidateShadow] instead of all
> three lines or just instead of the last two. The shadow shape is computed
> from the visible content of the window. That's why there's a call to -disp
OK Thanks Marco. Thad did the trick!!!
As I was suspecting, my "Mac" mind was hiding the solution from me. I didn't
guess that the UIWebView had its own internal UIScrollView to support all the
navigation gestures (scroll, zoom, rotate, translate etc.)
On the Mac, usually a view is usuall
On Apr 23, 2013, at 17:39:17, Mike Abdullah
wrote:
> -hasUnautosavedChanges continues to be applicable to all (auto)saving models.
>
> I caution against overriding it since:
>
> A) Your override is likely a lie to the system when you get down to it. This
> might upset the state for other bits
On 23 Apr 2013, at 15:19, Jerry Krinock wrote:
>
> On 2013 Apr 22, at 21:42, Steve Mills wrote:
>
>> [-setAutosavingDelay:0.0] didn't work.
>
> OK, then. I retract my surprise.
>
>> The pause mechanism is something in our own code - a bool that says it's
>> paused (it's actually an integer
On Apr 23, 2013, at 5:55 AM, Robert Vojta wrote:
> I do use borderless & transparent NSWindow with shadow. The way I do
> initialize this window is at the end of this email. I experienced lot of
> problems with shadow, but found in Apple examples that the only way to fix
> shadow (= read to dis
Hallo all,
I do use borderless & transparent NSWindow with shadow. The way I do initialize
this window is at the end of this email. I experienced lot of problems with
shadow, but found in Apple examples that the only way to fix shadow (= read to
display it correctly) is to call …
[self displ
OK Thanks Marco. Thad did the trick!!!
As I was suspecting, my "Mac" mind was hiding the solution from me. I didn't
guess that the UIWebView had its own internal UIScrollView to support all the
navigation gestures (scroll, zoom, rotate, translate etc.)
On the Mac, usually a view is usuall
I have a textview that is binding to Core data, I want to be able to
highlight the selected text in the textview.
*[self.textStorage addAttribute:NSBackgroundColorAttributeName value:[
NSColor yellowColor] range:self.selectedRange];*
The code above works, but core data won't save the attributes c
I'd like my IKCameraDeviceView to report downloaded images in memory-mode, but
despite the fact that I have told it to use
IKCameraDeviceViewTransferModeMemoryBased and it agrees that it heard me:
(gdb)p (int) [cameraDeviceView mode]
$1 = 1
... it still passes the image as a URL to its delegate
On 2013 Apr 23, at 08:18, Steve Mills wrote:
> What do you mean by "not running the show in Lion autosave"? As opposed to
> 10.8 and later, or 10.6 and earlier? (Please use numbers, as it's easier to
> remember the order of numbered versions.)
When I say "Lion Autosave", I mean this feature,
On Apr 23, 2013, at 09:19:47, Jerry Krinock wrote:
> That's fine, but your code is not running the show in Lion autosave. The
> holy grail we're discussing here is a method to tell Cocoa "Stop sending me
> autosave requests (-[NSDocument
> autosaveWithImplicitCancellability:completionHandler
On 2013 Apr 22, at 21:42, Steve Mills wrote:
> [-setAutosavingDelay:0.0] didn't work.
OK, then. I retract my surprise.
> The pause mechanism is something in our own code - a bool that says it's
> paused (it's actually an integer so it can be incremented/decremented in a
> nested fashion).
On 22 Apr 2013, at 23:57, Jerry Krinock wrote:
>
> On 2013 Apr 22, at 09:43, Steve Mills wrote:
>
>> So to sum up, upon pausing autosave
>
> which, per previous messages in this thread, I presume you do by sending the
> shared document controller -setAutosavingDelay:0.0. I'm surprised that
13 matches
Mail list logo
