In my application, I use Spotlight at some point to find a number of images in
a directory tree the user selects.
Now, I have one user who reports that it is not finding anything (it should
turn up all the images).
The problem seems to have to do with the directory residing on an external
share
Okay, I have this wild and crazy idea. I've got a UITableView with cells that
have different heights. The cells' content consists almost entirely of
UILabels, and the height of each cell depends on what's going to go into those
labels - the cell needs to grow to accommodate the text of the label
How can I find the row of an NSTableRowView?
When I print the object in the debugger it tells me which row, but I can't see
how it finds this...
po thisRowView
(NSTableRowView *) $1 = 0x000101d53fb0 - row:
1
Thanks,
Adam
___
Cocoa-dev maili
On Nov 2, 2012, at 12:24 AM, Rick Mann wrote:
> My somewhat older project has a couple of userInfo entries on each of the
> attributes in the Core Data model:
>
> com.apple.syncservices.AutomaticResolutionPolicy = {
>PreferredClientType = app;
>PreferredRecord = Truth;
> }
> com.apple.
Cells are sized according to the value returned from heightForRowAtIndexPath:.
You could theoretically call sizeToFit: on a cell you create inside that method
to get a height, but it would be very expensive to create a cell for every call
to this method. One technique you might try is to create
I may be misunderstanding what you mean by
> After run that simple app works improperly.
Does that mean you've fixed the simple app and its behavior still wrong? Or do
you mean you haven't and want us to debug your "real code" without knowing
anything about it?
If you have now implemented all
On Nov 2, 2012, at 8:19 AM, devl...@mac.com wrote:
> How can I find the row of an NSTableRowView?
>
> When I print the object in the debugger it tells me which row, but I can't
> see how it finds this...
>
> po thisRowView
> (NSTableRowView *) $1 = 0x000101d53fb0 -
> row: 1
Ask the table
This question relates to an iOS project, iOS 5 or later, developed on 10.8.2
using Xcode 4.5.1, testing with the iOS Simulator (5.0, 5.1, or 6.0).
I have a new project which uses a reasonably complex Core Data data model.
There are 10 entities with multiple relationships between them, and a coup
This code:
NSString *key = @"กุญแจ";
NSString *value = @"คุณค่า";
NSArray *array = @[ key, value ];
NSLog(@" Two nice strings: %@ %@", key, value);
NSLog(@" Bad Array: %@", array);
prints:
2012-...] Two nice strings: กุญแจ คุณค่า
2012-...] Bad Array: (
"\U0e01\U0e38\U0e0d\U0e41\U0e08",
On Nov 2, 2012, at 9:03 AM, Luke Hiesterman wrote:
> Cells are sized according to the value returned from heightForRowAtIndexPath:
Obviously. And that is why I am calculating (in advance) the value that I will
return from heightForRowAtIndexPath:. I've been doing that for years. The
question
UITableViewCell doesn't currently support autolayout, so no, you won't be able
to have the constraints system calculate the height for you.
Luke
On Nov 2, 2012, at 10:10 AM, Matt Neuburg wrote:
>
> On Nov 2, 2012, at 9:03 AM, Luke Hiesterman wrote:
>
>> Cells are sized according to the valu
On Nov 2, 2012, at 10:14 AM, Luke Hiesterman wrote:
> UITableViewCell doesn't currently support autolayout
I guess I'm having a little trouble understanding what that means. I am placing
content interface inside the content view of a UITableViewCell and handing
constraints to the cell, and au
On Fri, Nov 2, 2012, at 10:02 AM, Gerriet M. Denkmann wrote:
> This code:
>
> NSString *key = @"กุญแจ";
> NSString *value = @"คุณค่า";
> NSArray *array = @[ key, value ];
> NSLog(@" Two nice strings: %@ %@", key, value);
> NSLog(@" Bad Array: %@", array);
>
> prints:
>
> 2012-...] Two nice stri
On Nov 2, 2012, at 10:22 AM, Matt Neuburg
wrote:
>
> On Nov 2, 2012, at 10:14 AM, Luke Hiesterman wrote:
>
>> UITableViewCell doesn't currently support autolayout
>
> I guess I'm having a little trouble understanding what that means. I am
> placing content interface inside the content view
Aha. Yes, I did notice that I couldn't make constraints involving e.g. the
built-in textLabel object; it's as if it wasn't even in the interface.
The second part of your answer, that not being in the view hierarchy means the
autolayout engine won't operate, is the answer to my original question;
Gerriet M. Denkmann wrote:
2012-...] Bad Array: (
"\U0e01\U0e38\U0e0d\U0e41\U0e08",
"\U0e04\U0e38\U0e13\U0e04\U0e48\U0e32"
)
For a very long time, the -description method of NSArray (and other
collection classes) has produced the old-style ASCII plist format.
Since that format h
On Nov 2, 2012, at 9:01 , Nick Zitzmann wrote:
> Those look like Sync Services properties. Sync Services was a way of
> synchronizing data between applications and computers back in the days when
> PCs were still peoples' digital hubs. In Leopard (I think) Apple added the
> option to directly
Hello,
I am trying to write a customized video player, and I would like to have a
slider showing and controlling the QTMovie progress. I am using QTKit
(since I need Snow Leopard support, which is still widely used).
I have placed an NSSlider onto the view, and set it to "Continuous", so
that it
On Nov 2, 2012, at 10:41 AM, Luke Hiesterman wrote:
> it's not in the view hierarchy, in which case the autolayout engine won't do
> anything for you
Okay, the good news is that this turns out to be false! It turns out that you
*can* exercise the autolayout engine for any view hierarchy by sen
Is there a Core Foundation replacement for FSFindFolder? I'm reluctant to use
Cocoa functions in my framework. As it is, I'm using an absolute path to get to
a folder in Application Support in both the local and user libraries.
___
Cocoa-dev mailing l
On Fri, 2 Nov 2012 18:50:27 -0600, C.W. Betts said:
>Is there a Core Foundation replacement for FSFindFolder?
I don't think so. Today's recommendation is NSFileManager's
URLForDirectory:inDomain:appropriateForURL:create:error:.
>I'm reluctant
>to use Cocoa functions in my framework.
Why?
>As
Aand here's the code! Oddly, I never did quite solve the problem I
originally set out to solve; everything was happening correctly except that at
the last minute the cell was snapping back to its original size, even though
the constraints said clearly enough that it should not. However,
On 3 Nov 2012, at 00:35, Kyle Sluder wrote:
> On Fri, Nov 2, 2012, at 10:02 AM, Gerriet M. Denkmann wrote:
>> This code:
>>
>> NSString *key = @"กุญแจ";
>> NSString *value = @"คุณค่า";
>> NSArray *array = @[ key, value ];
>> NSLog(@" Two nice strings: %@ %@", key, value);
>> NSLog(@" Bad Array:
On Nov 2, 2012, at 22:18 , "Gerriet M. Denkmann" wrote:
> Is there a way to make the first NSLog work?
> I seem to remember that it calls something like debuggingDescription, which,
> if not overridden calls description.
>
> I have no experience with swizzling.
Aren't you making things rather
24 matches
Mail list logo
