I've got a UITableView within another view on a storyboard as in the example
here:
https://docs.google.com/file/d/0B3FbUXsjem4pcFJkeWpTVzVRdVU/edit?pli=1
In my storyboard, the rect of the UITableView is (0, 313, 768, 598), and I am
navigating to the scene ala a segue.
But as soon as viewDidLo
Thanks for all replies.
Now I know that event ID is related with device UUID.
And about FSEventStore, I google it but I can not found any information
of this.
can you provide some information of this ?
Alfian.
On 12/07/31 9:53, Ron Hunsinger wrote:
On Jul 30, 2012, at 4:47 AM, Robert Martin
Have you connected an IBOutlet from code & then linked it in storyboard? I
assume you are programmatically setting the frame on this IBOutlet. And,
Did you check the Table View object's autosizing in Storyboard?
To debug, you can try adding another table view object (ignore the
problematic one) co
On Tue, Jul 31, 2012 at 6:19 AM, Richard Somers wrote:
>
> This might help.
>
>
> http://www.cocoabuilder.com/archive/cocoa/145464-nstextview-auto-scroll-up-behaviour.html
>
>
Thanks for the reply! However, it does not seem to work - it still scrolls
half-page up/down, even if I change the "margin
On 30 Jul 2012, at 19:40, David Duncan wrote:
You are going to have to define what you mean by start & end, as it
is not clear in context.
If you mean a visual location, then neither of these methods are
going to do what you want. You would put something visually at the
start/end of the
Ahh, thought I caught this before it went out.
In any case, it appears that setting the frame of a UITableView doesn't do
anything on viewDidLoad, or viewWillAppear, but does work on viewDidAppear.
And the reason the tableView didn't obey the storyboard settings was that the
parent view wasn't
On Jul 31, 2012, at 3:52 AM, Dave wrote:
> The above is basically what I'd like to do, hold a number of pages/images
> "around" the current page and when the user Scrolls left or right replace the
> appropriate pages/images with newly rendered versions.
So it sounds like you want the views to
On Jul 31, 2012, at 03:52 , Dave wrote:
> Basically I have process that generates UIImage's and each of these images
> needs to be presented in a Scroll View. However there can be a large number
> of images generated and each image is pretty big too, so obviously, it can't
> hold them all in R
I am having weird results with NSTask. It sometimes retrieves the output, and
other times receives nothing.
I have example code for this issue at
https://dl.dropbox.com/u/610721/NSTask%20Issue.zip
The result I have is below:
0 Starting
0 Received /bin/ls
0 Done
1 Starting
1 Received
1 Done
2 S
On 31 Jul 2012, at 3:33 PM, Mr. Gecko wrote:
> I am having weird results with NSTask. It sometimes retrieves the output, and
> other times receives nothing.
I haven't looked at the code you posted, but is it possible that you're reading
from the NSPipe in such a way that you're mixing up the "e
What do you recommend after the task finishes? I have tried [[outPipe
fileHandleForReading] readDataToEndOfFile] after the task finishes and it
doesn't seem to improve. Can you maybe give me an example of how to do this
right?
On Jul 31, 2012, at 6:01 PM, Wim Lewis wrote:
> I haven't looked a
On Tue, Jul 31, 2012, at 03:33 PM, Mr. Gecko wrote:
> I am having weird results with NSTask. It sometimes retrieves the output,
> and other times receives nothing.
>
> I have example code for this issue at
> https://dl.dropbox.com/u/610721/NSTask%20Issue.zip
NSTask requires a running runloop. You
I have multiple run loops.
On the main thread I have [[NSRunLoop currentRunLoop] run];
On the sub threads for NSTask and NSPipe, I have
CFRunLoopRunInMode(kCFRunLoopDefaultMode, 1, YES);
If you are saying that you have to use NSRunLoop in order for it to work, get
it working in my example and
On Jul 31, 2012, at 6:53 PM, "Mr. Gecko" wrote:
>
> I can confirm if you do not stop the run loop, it will get everything…
> However… I cannot do this as I do not know how much data I am receiving from
> the task.
1) Yes, you need to run the run loop forever (NSDistantFuture).
2) You don't n
I need threads because the main thread is a network loop waiting for a
connection and when it gets a connection, it spawns a thread like in my
example. I need to be able to respond to the client with all the data from the
task and I need to close out the connection and release the spawned
threa
On Jul 31, 2012, at 7:43 PM, Mr. Gecko wrote:
> I need threads because the main thread is a network loop waiting for a
> connection and when it gets a connection, it spawns a thread like in my
> example. I need to be able to respond to the client with all the data from
> the task and I need t
We have a problem where some underlying data changes, so we go through
the annotation collection for a mapview and change the affected
annotation (in this case its title); and when the associated marker on
the map is tapped, the displayed text isn't changed.
In other cases, an annotation is delete
On 2012 Jul 28, at 21:48, Lee Ann Rucker wrote:
> Use Accessibility. There's a utility called Moom that does that.
or AppleScript; moving windows is in the Standard Suite, so I think any app
which announces itself as scriptable can have its windows moved.
Neither way is 100% reliable. Access
NSPipe itself doesn't require that a run loop be run, but the
"InBackgroundAndNotify" methods of the associated NSFileHandle objects do.
You receive a zero-length NSData when (and only when) a read encounters EOF.
There is an inherent race between the receipt of the task termination
notificatio
On 30 Jul, 2012, at 17:53, Ron Hunsinger wrote:
>
> On Jul 30, 2012, at 4:47 AM, Robert Martin wrote:
>
>> Just keep track of the device UUID for each path and last event ID that
>> you're tracking. EventID's are tied to each device, so you have to know that
>> the device has not changed behi
The NSSortDescriptor documentation seems especially opaque to me tonight.
Surely there is a useful short description somewhere … ? *whimper*
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator commen
On 01/08/2012, at 3:01 PM, Erik Stainsby wrote:
> The NSSortDescriptor documentation seems especially opaque to me tonight.
> Surely there is a useful short description somewhere … ? *whimper*
Sort descriptors are quite easy to use - what's the specific problem?
warning: typed into Mail:
N
On 01/08/2012, at 3:07 PM, Graham Cox wrote:
> NSSortDescriptor* desc = [NSSortDescriptor sortDescriptorWithKey:@"compare:"
> ascending:YES];
Oops, this wasn't what I meant.
The "key" should be the property you're comparing to sort the objects. If your
array is a bunch of strings to be sorte
This has me thinking that to get the alpha sorted list of keys from a
dictionary I should be passing the keypath as the param for
sortDescriptorWithKey: and not trying to externalize the keys into an array
first … ?
On 2012-07-31, at 10:13 PM, Graham Cox wrote:
>
> On 01/08/2012, at 3:07 PM
On 01/08/2012, at 3:20 PM, Erik Stainsby wrote:
> This has me thinking that to get the alpha sorted list of keys from a
> dictionary I should be passing the keypath as the param for
> sortDescriptorWithKey: and not trying to externalize the keys into an array
> first … ?
If you want to itera
Never mind. The problem was an incomplete array of annotations I was maintaing.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)li
On Jul 31, 2012, at 11:18 PM, Jerry Krinock wrote:
> Neither way is 100% reliable. Accessibility probably requires that "Enable
> Access for assistive devices" be on in System Preferences. I don't see why
> we have that stupid checkbox. At least, in 10.8 it's on by default in a new
> accoun
27 matches
Mail list logo
