Not if your UITableView has only one section and you use the section's header
view in the way Marcelo suggests. Sections headers scroll up to the top and
then remain there - visible - while additional cells scroll underneath it…
Op Nov 27, 2013, om 4:30 AM heeft Rick Mann
Hi all,
I have an application which monitors the iTunes plist file to control the
Parental tab settings and I am running to an issue on Mavericks 10.9.
On Mountain Lion 10.8.x and Lion OS X 10.7.x , I would monitor and update
the plist file present at path
Multiple sections.
--
Rick
On Nov 27, 2013, at 1:03, Diederik Meijer | Ten Horses
diede...@tenhorses.com wrote:
Not if your UITableView has only one section and you use the section's header
view in the way Marcelo suggests. Sections headers scroll up to the top and
then remain there
I do the following, the property *tableView in UITableViewController is not
backed by a _tableView instance variable, so I synthesize that (@synthesize
tableView = _tableView;) and then in viewDidLoad:
if (!_tableView [self.view isKindOfClass:[UITableView class]])
self.tableView =
On Nov 27, 2013, at 01:37 , Ray Raphaël cocoa-...@deployedsmarts.com wrote:
I do the following, the property *tableView in UITableViewController is not
backed by a _tableView instance variable, so I synthesize that (@synthesize
tableView = _tableView;) and then in viewDidLoad:
if
On 21 Nov 2013, at 22:29, jonat...@mugginsoft.com wrote:
Looking at the action responder chain for a document based app (fig 1-10):
https://developer.apple.com/library/mac/documentation/cocoa/conceptual/eventoverview/EventArchitecture/EventArchitecture.html
This shows that the action
On Nov 27, 2013, at 1:10 AM, Arjun SM arjun...@gmail.com wrote:
Hi all,
I have an application which monitors the iTunes plist file to control the
Parental tab settings and I am running to an issue on Mavericks 10.9.
Editing plist files directly is not and has never been a supported way of
On Nov 26, 2013, at 9:56 PM, Rick Mann rm...@latencyzero.com wrote:
In my ongoing experimentation with getting a fixed view above my table view,
I'm trying to do what I did successfully in the days before autolayout:
separate the UITV's view and tableView properties. This works, but I
NSString *scriptPath = [[NSBundle mainBundle] pathForResource:@DeleteHidden
ofType:nil];
NSTask *task;
task = [[NSTask alloc] init];
[task setLaunchPath:scriptPath];
The script DeleteHidden had line endings of cf,lf which caused an exception
on 10.9
removing the cr via a hex editor resolved
On Nov 27, 2013, at 7:59 AM, koko k...@highrolls.net wrote:
NSString *scriptPath = [[NSBundle mainBundle] pathForResource:@DeleteHidden
ofType:nil];
NSTask *task;
task = [[NSTask alloc] init];
[task setLaunchPath:scriptPath];
The script DeleteHidden had line endings of cf,lf which
Roland is 100% correct here. You can't reliably predict what the device
identifiers will be and filing bugs is the best way to register your needs.
The fact that you could guess device identifiers has more to do with the fact
that there have only been 2 released generations of the iPad mini and
Apparently, OS X 10.9 caches preference files. This is the first I’ve heard
about it (on a discussion on Ars Technica of all places). Is there any
documentation about this, like an explanation as to what purpose this has?
I noticed recently that after deleting my app’s prefs file, I was still
The preferences file has always been considered an implementation detail. I'm
not up on all the reasons for the change, but you should be able to use the
'defaults' command line tool to do the same thing that trashing prefs used to
do. Something like 'defaults delete com.yourcompany.yourapp'
On 27 Nov 2013, at 8:18 pm, David Duncan david.dun...@apple.com wrote:
The preferences file has always been considered an implementation detail. I'm
not up on all the reasons for the change, but you should be able to use the
'defaults' command line tool to do the same thing that trashing
While I agree that sometimes deleting a prefs file is useful, its not really a
good idea - never was. Its still asking the user to muck around app internals.
The fact that mavericks now caches really shouldn’t matter.
I think if deleting your prefs file is a common case, or even somewhat
On Wed, Nov 27, 2013, at 11:27 AM, Graham Cox wrote:
Really, Apple are supposed to be the champions of the average user aren’t
they? Have they talked to any recently? Honestly, it would serve everyone
well if every developer served a month in a call centre.
If you think deleting a plist in
On Nov 27, 2013, at 2:18 PM, David Duncan david.dun...@apple.com wrote:
The preferences file has always been considered an implementation detail. I'm
not up on all the reasons for the change, but you should be able to use the
'defaults' command line tool to do the same thing that trashing
On 27 Nov 2013, at 8:42 pm, Kyle Sluder k...@ksluder.com wrote:
If you think deleting a plist in ~/Library/Preferences is a solution
to any problem to which run `defaults delete` is not, I think you're
concerned about a very narrow definition of average user.
Well, I’m more concerned about
On Wed, Nov 27, 2013, at 11:53 AM, Graham Cox wrote:
So let me turn this into a dev question then. Do I need to actually run a
command line task to do this, or is there some API I can use? For
example, what does + resetStandardUserDefaults achieve? Anything useful
in this case?
Not what you
On 27 Nov 2013, at 9:00 pm, Kyle Sluder k...@ksluder.com wrote:
On Wed, Nov 27, 2013, at 11:53 AM, Graham Cox wrote:
So let me turn this into a dev question then. Do I need to actually run a
command line task to do this, or is there some API I can use? For
example, what does +
On 27 Nov 2013, at 9:12 pm, Graham Cox graham@bigpond.com wrote:
Not what you want.
Use -[NSUserDefaults removePersistentDomainForName:] with your app's
bundle ID.
Thanks, that’s a good one to know. The documentation doesn’t even begin to
suggest this method would be appropriate.
On Nov 27, 2013, at 11:53 AM, Graham Cox wrote:
On 27 Nov 2013, at 8:42 pm, Kyle Sluder k...@ksluder.com wrote:
If you think deleting a plist in ~/Library/Preferences is a solution
to any problem to which run `defaults delete` is not, I think you're
concerned about a very narrow
On 27 Nov 2013, at 10:20 pm, Lee Ann Rucker lruc...@vmware.com wrote:
If they're that naive a user, they can't navigate the GUI to get to the prefs
- ~/Library has been hidden by default for years now.
Yes, that was a bit of a headache when the folder was hidden by default, and we
had to
On Nov 27, 2013, at 11:53 , Graham Cox graham@bigpond.com wrote:
in many cases I’m afraid “trashing the prefs” is akin to voodoo as a solution
for a problem, but it’s often put out there (not by us if we really don’t
think it will help I hasten to add).
Adding a button it is, I agree
On 27 Nov 2013, at 10:43 pm, Quincey Morris
quinceymor...@rivergatesoftware.com wrote:
FWIW I would say: right diagnosis, wrong solution.
What on earth is going on with your app(s) that requires preferences to be
deleted? If, after all these years of your being a very accomplished
On Nov 27, 2013, at 14:12 , Graham Cox graham@bigpond.com wrote:
We’ve had rare cases in the past where a prefs file has caused an issue.
Obviously we did not anticipate it, otherwise it would have been discovered
in testing and fixed before it got out into the wild, but we know that
On Nov 27, 2013, at 07:36 , Kyle Sluder k...@ksluder.com wrote:
Either way, the relationship between a UITVC's view and tableView is not
yours to modify. In the time you've spent trying to hack this, you could have
moved your cells to XIBs and implemented a static data source in your own
What on earth is going on with your app(s) that requires preferences to be
deleted? If, after all these years of your being a very accomplished
developer, your apps aren’t robust enough to deal with unusable or
inconsistent values in prefs — or, more to the point, put the prefs into such
On Nov 27, 2013, at 15:15 , Marco S Hyman m...@snafu.org wrote:
Tell that to Apple.
Dear Apple, you have a major bug in Final Cut Pro that causes it to go
kerflooey when its preferences get into a state it doesn’t expect. Please fix
it.
Marco, don’t you agree that (now, 10+ years into the OS
On 28 Nov 2013, at 7:53 AM, Graham Cox graham@bigpond.com wrote:
I guess if/when it crops up again we’ll just have to navigate the unfortunate
user through the command line.
Or write a one-line AppleScript script:
do shell script defaults delete ...
Save it as a code-signed app, send it
A universal app.
On iPad:
UIView:; frame = (321 0; 447 1024); with three subviews (top to bottom);
UINavigationBar:; frame = (0 0; 447 44); opaque = NO; autoresize =
W+BM;
UIWebView: frame = (0 44; 447 936); clipsToBounds = YES; autoresize =
W+H;
UIToolbar:;
31 matches
Mail list logo
