On Oct 20, 2013, at 12:27 AM, Trygve Inda wrote:
> My question is: After I have an NSPredicate built by the user with the
> Predicate editor, how can determine the keys that the NSPredicate uses?
You need to traverse the hierarchy of objects represented by the predicate.
The NSPredicate you have
> On Oct 19, 2013, at 10:44 PM, Trygve Inda wrote:
>
>> I have an array of objects. These objects may have some dynamic properties
>> handled with valueForUndefinedKey.
>>
>> If I create a predicate along the lines of:
>>
>> myObject.proertyA = something AND
>> myObject.proertyB = somethingElse
On Oct 19, 2013, at 10:44 PM, Trygve Inda wrote:
> I have an array of objects. These objects may have some dynamic properties
> handled with valueForUndefinedKey.
>
> If I create a predicate along the lines of:
>
> myObject.proertyA = something AND
> myObject.proertyB = somethingElse AND
> myObj
I have an array of objects. These objects may have some dynamic properties
handled with valueForUndefinedKey.
If I create a predicate along the lines of:
myObject.proertyA = something AND
myObject.proertyB = somethingElse AND
myObject.dynamicPropertyA = someOtherThing
How can I look at myPredic
I created a simple project that uses a modal window. The quit
execution works are stated in the docs even though the window is modal.
Which means I am doing something wrong. More investigating to do.
On
19/10/2013, at 3:01 PM, Ken Thomases wrote:
> On Oct 18, 2013, at
6:35 PM, trid...@ihu
Rather than rely on intercepting responder chain-based validation, wouldn't it
be much easier and more reliable to make some object the delegate of all of
your NSMenus and implement -menuNeedsUpdate:?
--Kyle Sluder
> On Oct 19, 2013, at 1:28 PM, Andy Lee wrote:
>
> Uli and I both remembered t
Uli and I both remembered the app delegate is checked *after* the
window-related objects in the responder chain, which is what you discovered.
I *thought* you could work around this by changing the actions of the Close
menu items to methods that only the app delegate implements. But you really
On Oct 19, 2013, at 12:28 PM, Martin Hewitson
wrote:
> OK, so the idea is,
>
> + validateMenuItem in app delegate gets a first shot at setting the keyboard
> shortcuts
> + I override validateMenuItem in my tabbed window and reset the keyboard
> shortcuts
> + Other windows stick with the setti
On 19, Oct, 2013, at 08:59 pm, Michael Babin wrote:
> On Oct 19, 2013, at 1:32 PM, Martin Hewitson
> wrote:
>
>> I guess I didn’t understand correctly since my app delegate does not get
>> asked to validate the Close menu item. So far the only thing that get’s
>> asked to validate this is t
On Oct 19, 2013, at 1:32 PM, Martin Hewitson wrote:
> I guess I didn’t understand correctly since my app delegate does not get
> asked to validate the Close menu item. So far the only thing that get’s asked
> to validate this is the tabbed window object. Even the window’s delegate is
> not ask
I guess I didn’t understand correctly since my app delegate does not get asked
to validate the Close menu item. So far the only thing that get’s asked to
validate this is the tabbed window object. Even the window’s delegate is not
asked.
The documentation states:
For document-based application
I’ve considered that as my last resort - I’m not against code as I normally do
most of my work in code and don’t use NIBs as much as I probably should - but
I’m trying to see what is possible via storyboards and a bit of code.
On Oct 18, 2013, at 9:44 PM, Richard Heard wrote:
> Seems like a c
OK, so the idea is,
+ validateMenuItem in app delegate gets a first shot at setting the keyboard
shortcuts
+ I override validateMenuItem in my tabbed window and reset the keyboard
shortcuts
+ Other windows stick with the settings arranged by the app delegate
Did I understand correctly?
Thanks
On 2013 Oct 19, at 03:38, jonat...@mugginsoft.com wrote:
> I don't know if this is a common technique but I use it regularly to track
> binding changes.
>
> - (void)setValue:(id)value forKeyPath:(NSString *)keyPath
> {
>// all bindings that reference self (such as self.representedObject.xxx
libclang is more than that.
Xcode code highlighting and code indexing is based on lib clang, as well as
delta compilation. (and I have a remote plan of cloning Xcode for GNUstep)
Also, there was a friend of mine that created a translator that converts code
from a new language to C, and I modifi
Le 19 oct. 2013 à 15:01, Uli Kusterer a écrit :
> On 19 Oct 2013, at 01:17, Shane Stanley wrote:
>> On 19 Oct 2013, at 3:15 AM, Uli Kusterer
>> wrote:
>>
>>> this is what you'd do if you wanted to make e.g. CoreFoundation APIs
>>> accessible to a scripting language
>>
>> That's along the l
On Oct 19, 2013, at 9:04 AM, Andy Lee wrote:
> My first thought was that the app delegate might not get a validateMenuItem:
> message if something earlier in the responder chain handles those menu items.
> But you could change the actions of the menu items to something unique to
> make sure no
On 19 Oct 2013, at 15:04, Andy Lee wrote:
> My first thought was that the app delegate might not get a validateMenuItem:
> message if something earlier in the responder chain handles those menu items.
> But you could change the actions of the menu items to something unique to
> make sure nothi
On Oct 19, 2013, at 8:46 AM, Uli Kusterer wrote:
>
> On 19 Oct 2013, at 14:27, Andy Lee wrote:
>> On Oct 19, 2013, at 6:58 AM, Martin Hewitson
>> wrote:
>>> Main Window with tabs:
>>> close (cmd-shift-w)
>>> close tab (cmd-w)
>>>
>>> All other windows:
>>> close (cmd-w)
>>>
On 19 Oct 2013, at 01:17, Shane Stanley wrote:
> On 19 Oct 2013, at 3:15 AM, Uli Kusterer wrote:
>
>> this is what you'd do if you wanted to make e.g. CoreFoundation APIs
>> accessible to a scripting language
>
> That's along the lines of what I had in mind, although in this case for basic
>
On 18 Oct 2013, at 20:38, Kyle Sluder wrote:
> CFBundleGetFunctionPointerForName just calls dlsym.
Sure. NSLog also eventually calls syslog. I still wouldn’t drop down to syslog
for most Cocoa logging needs.
CFBundleGetFunctionPointerForName takes a CFStringRef and if you’re e.g.
looking at a
On 19 Oct 2013, at 14:27, Andy Lee wrote:
> On Oct 19, 2013, at 6:58 AM, Martin Hewitson
> wrote:
>> Main Window with tabs:
>> close (cmd-shift-w)
>> close tab (cmd-w)
>>
>> All other windows:
>> close (cmd-w)
>> close tab (inactive, no keyboard shortcut)
>>
>> This is pre
On Oct 19, 2013, at 6:58 AM, Martin Hewitson wrote:
> Main Window with tabs:
> close (cmd-shift-w)
> close tab (cmd-w)
>
> All other windows:
> close (cmd-w)
> close tab (inactive, no keyboard shortcut)
>
> This is pretty much the way things work in Xcode.
>
> So, my qu
Dear list,
I have an app with tabs and I’m trying to change the default 'close' keyboard
equivalent for only the main window which has the tabs. I’d like to have
Main Window with tabs:
close (cmd-shift-w)
close tab (cmd-w)
All other windows:
close (cmd-w)
close t
On 19 Oct 2013, at 03:58, Jerry Krinock wrote:
>
> In Core Data documents, I ignore -[NSDocument isDocumentEdited] and instead
> use
> -[NSManagedObjectContext hasChanges].
>
> "In OS X v10.6 and later, this property is key-value observing compliant."
>
Unfortunately I am not using CoreData
Thanks Gideon.
Turning on the layer backing for all those levels did fix the redrawing problem.
I didn't find out how to fix the layer drawing when the bounds origin has been
moved, but I did work out a workaround.
I added an instance variable to my view (the scrollview's document view):
@pro
26 matches
Mail list logo
