Please understand that I do not wish to get anyone in trouble. It is
common for heads to roll over product defects. That is not even
remotely my objective.
To be perfectly clear: this is a widespread, systemic problem in many
industries but in my own experience and that of many others it is
part
Hi,
I am implementing two custom classes, one of them is the document view inside
an NSScrollView and the other is a subview of the document view. I need to
create two NSTrackingArea’s to display the appropriate cursor when the mouse
hovers over specific areas of the subviews. As instructed by
Hi J.Varela,
i too faced the same problem... and i found that "inertial scrolling" has
the reason for this misbehaviour.
so "disable the inertia scrolling" will solve this problem.
just add the following line to your application init method...
* [[NSUserDefaults standardUserDefaults] setBool
Same here. I ran QA for one of the Director and Shockwave teams at Macromedia
back in the mid 1990s.
Based on the result of effort put in to reporting bugs and amount fixed, there
is no way I can justify reporting bugs even if I had the time to afford to do
it. The time lost (that our employer
Thanks, Has. This looks great.
Sent from my iPhone
> On Jul 13, 2015, at 10:25 AM, has wrote:
>
> Hi all,
>
> In light of OS X 10.11 addressing some longstanding deficiencies in
> NSAppleEventDescriptor, I've been dusting off a fork of my old objc-appscript
> project, now renamed AppleEventB
> On 15 Jul 2015, at 18:38, Alex Zavatone wrote:
>
> Based on the result of effort put in to reporting bugs and amount fixed,
> there is no way I can justify reporting bugs even if I had the time to afford
> to do it.
Well it depends. If we’re talking bug reporting to , that’s one thing. Bu
Yet in the time you spent wasting keystrokes on this thread, you both could
easily have filed bugs.
> On Jul 15, 2015, at 8:38 PM, Alex Zavatone wrote:
>
> Same here. I ran QA for one of the Director and Shockwave teams at Macromedia
> back in the mid 1990s.
>
> Based on the result of effo
On Jul 15, 2015, at 8:07 AM, 2551 wrote:
>
>> On 15 Jul 2015, at 18:38, Alex Zavatone wrote:
>>
>> Based on the result of effort put in to reporting bugs and amount fixed,
>> there is no way I can justify reporting bugs even if I had the time to
>> afford to do it.
>
> Well it depends. If
> On Jul 15, 2015, at 1:18 AM, Michael David Crawford
> wrote:
>
> Please understand that I do not wish to get anyone in trouble. It is
> common for heads to roll over product defects. That is not even
> remotely my objective.
Take it to Reddit and leave us alone.
-rags
__
On 7/15/15, dangerwillrobinsondan...@gmail.com
wrote:
> Yet in the time you spent wasting keystrokes on this thread, you both could
> easily have filed bugs.
In the time I could have wasted by filing bugs, I actually did write:
I State This That It May Be Rejected:
The Lysistrata Manifesto
On 7/15/15, Raglan T. Tiger wrote:
> Take it to Reddit and leave us alone.
Thanks for setting me straight. I didn't realize that Apple's
engineers hang out at Reddit.
Mike
--
Michael David Crawford, Consulting Software Engineer
mdcrawf...@gmail.com
http://www.warplife.com/mdc/
Available fo
> On Jul 15, 2015, at 7:45 AM, Michael David Crawford
> wrote:
>
> I didn't realize that Apple's
> engineers hang out at Reddit.
They do not. Nutcases do.
-rags
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin reque
On Jul 15, 2015, at 03:08 , João Varela wrote:
>
> However, none of this happens when the user only scrolls (up or down) a
> little and does not reach the top or bottom of the document view. In this
> case, not only the -updateTrackingAreas method of the subview is not called,
> but also the c
Hi Alex,
Thanks for the kind words. I know AEB's off to a hopeful start: I've
been using appscript professionally for high-end automation for
years[1], and hundreds (thousands?) of other appscript users have beaten
the tar out of it over the years too, so the design has already proven
itself.
Quick postscript: I've now posted AppleEventBridge's Swift documentation
online for easier perusal:
http://hhas.bitbucket.org/
It's still a bit rough, natch, but it should give a good idea of what it
does and how it works without having to pull the project first.
HTH
has
___
In a sandboxed app, I do:
NSSavePanel* sp = [NSSavePanel savePanel];
[sp setAccessoryView:some_view];
This works 99% of the time, but sometimes it just crashes. This seems to occur
when the app has just been activated after using a different app, and this save
panel is requested within a fe
Hi all,
I posted a question at SO
(http://stackoverflow.com/questions/31307331/how-to-use-nssecurecoding-with-id-objects)
and despite the bounty it still didn't get any answers. I am not confident
that it will either.
The problem is when implementing NSSecureCoding with a collection (or
contain
> On Jul 15, 2015, at 3:53 PM, Graham Cox wrote:
>
> This works 99% of the time, but sometimes it just crashes. This seems to
> occur when the app has just been activated after using a different app, and
> this save panel is requested within a few seconds of the activation, though
> that’s a
> On 16 Jul 2015, at 11:01 am, Conrad Shultz wrote:
>
>
>> On Jul 15, 2015, at 3:53 PM, Graham Cox wrote:
>>
>> This works 99% of the time, but sometimes it just crashes. This seems to
>> occur when the app has just been activated after using a different app, and
>> this save panel is reque
> On 16 Jul 2015, at 08:30, André Francisco wrote:
>
> Hi all,
> I posted a question at SO
> (http://stackoverflow.com/questions/31307331/how-to-use-nssecurecoding-with-id-objects)
> and despite the bounty it still didn't get any answers. I am not confident
> that it will either.
> The proble
(I'm new to the mailing list and I'm not sure whether I should reply just to
Roland or everyone. Please correct me if I'm doing this wrong. I'm replying to
both)
This seems far from ideal, and I'm actually surprised about NSArray's
behaviour. The fact that it decodes a set of classes known to im
The list of things which the collection classes decode automagically is pretty
small, limited I think to the primitives in XML/Binary document. But yes you
can craft a document with an NSArray in it and subtypes and that will be
decoded into strings and numbers. That means if you use NSArray() o
This delegate method is passed a WKWebView whose URL property is nil, a
WKNavigation that doesn't have any information, and an NSError that has in its
userInfo dictionary a NSErrorFailingURLStringKey. But in iOS 9 this key is
marked as deprecated in iOS 7 and is thus unusable in Swift.
ViewCont
> On 16 Jul 2015, at 14:23, Rick Mann wrote:
>
> This delegate method is passed a WKWebView whose URL property is nil, a
> WKNavigation that doesn't have any information, and an NSError that has in
> its userInfo dictionary a NSErrorFailingURLStringKey. But in iOS 9 this key
> is marked as de
> On Jul 15, 2015, at 23:39 , Roland King wrote:
>
>
>> On 16 Jul 2015, at 14:23, Rick Mann wrote:
>>
>> This delegate method is passed a WKWebView whose URL property is nil, a
>> WKNavigation that doesn't have any information, and an NSError that has in
>> its userInfo dictionary a NSError
On Jul 15, 2015, at 23:23 , Rick Mann wrote:
>
> ViewController.swift:86:36: 'NSErrorFailingURLStringKey' is unavailable: APIs
> deprecated as of iOS 7 and earlier are unavailable in Swift
IDK, but in the NSError class reference documentation it says this was
deprecated in iOS 4.0 and the repl
> On Jul 15, 2015, at 23:44 , Quincey Morris
> wrote:
>
> IDK, but in the NSError class reference documentation it says this was
> deprecated in iOS 4.0 and the replacement is
> “NSURLErrorFailingURLStringErrorKey”, so I’d assume that’s the correct thing
> to use instead.
Ah, good catch. I
> On 16 Jul 2015, at 14:45, Rick Mann wrote:
>
>
>> On Jul 15, 2015, at 23:44 , Quincey Morris
>> wrote:
>>
>> IDK, but in the NSError class reference documentation it says this was
>> deprecated in iOS 4.0 and the replacement is
>> “NSURLErrorFailingURLStringErrorKey”, so I’d assume that’
28 matches
Mail list logo
