Hi,
Thanks for all the inputs.
The app doesn't run any scheduled operations.
So the situation would occur only when the user wants it to.
Best,
Nick
On 03-May-2013, at 10:26 AM, Kyle Sluder wrote:
> On Thu, May 2, 2013, at 09:16 PM, Nick Rogers wrote:
>> Hi,
>>
>> I want my app to delay force
On May 3, 2013, at 1:29 AM, Gerriet M. Denkmann wrote:
> I have a button which only makes sense when exactly one thing is selected.
> Currently it's Enabled property is bound to Array
> Controller.selectedObjects.@count.
> I.e. the button is enabled if one or more things are selected.
>
> But I
On May 3, 2013, at 1:01 AM, Nick Rogers wrote:
> Hi,
>
> Thanks for all the inputs.
> The app doesn't run any scheduled operations.
> So the situation would occur only when the user wants it to.
No. It will happen at the worst possible time.
Forced sleep is forced for a reason.
--Kyle Sluder
I have subclassed a NSView and placed it within a window.
In this NSView I have to align my NSBezier rect to the pixel grid and stroke
a perfect and aligned 1 pixel width rect.
So, in the documentView's drawRect: method, I do
[[NSGraphicsContext currentContext] setShouldAntialias:NO];
[NSBezierPa
On May 2, 2013, at 9:56 PM, Kyle Sluder wrote:
> This shouldn't happen. It's a bad thing when it does. So the system is
> designed to prevent you from causing it to happen.
>
> Please don't try to give your users a "Ruin My Hardware" checkbox.
The question is whether running the CPU while the
How do I force *all* NSDocument dialogs to be handled SYNCHRONOUSLY?
NSDocument continues to be a software maintenance nightmare.
Asynchronous NSDocument dialogs should be the exception, not the rule,
*especially* in these cases:
NSApp knows its being asked to terminate.
NSApp knows it hasn
On Fri, May 3, 2013, at 01:32 PM, Keith Knauber wrote:
> How do I force *all* NSDocument dialogs to be handled SYNCHRONOUSLY?
You don't.
>
> NSDocument continues to be a software maintenance nightmare.
I agree, but until Apple simplifies the API, correctly dealing with
NSDocument will simply re
On May 2, 2013, at 11:53 AM, Jens Alfke wrote:
> On May 1, 2013, at 5:10 AM, Motti Shneor wrote:
>
>> Currently, MyB retains itself within its thread, and releases itself just
>> before the thread exits. I know it is bad practice (self retaining objects),
>> but I did not yet think of a better
On 3 May 2013, at 17:07, Andy Lee wrote:
> On May 3, 2013, at 1:29 AM, Gerriet M. Denkmann wrote:
>> I have a button which only makes sense when exactly one thing is selected.
>> Currently it's Enabled property is bound to Array
>> Controller.selectedObjects.@count.
>> I.e. the button is enabl
Personally I would just use the value transformer approach. It's easy,
obvious, and discoverable. Any other solution I can think up with
would be lacking in at least one of these. I actually find value
transformers to be super helpful when working with bindings. I've used
one for an empty string (t
FWIW, I just had an SMS issue with my MPB that I have several SSDs in.
I hit a speed bump when driving home and this triggered the SMS which I swore I
set to off in the terminal. Well, I was wrong and somehow, the SMS triggered
while the device was closed and the device became hot enough to t
11 matches
Mail list logo
