I hear ya.
Keyboards, keystrokes and text management have always been so opaque on
iOS. I think that might make it easier for devs to get up and running but
if we're to write world class apps to compete with the desktop at all, I
think we're going to need better text handling abstractions.
Just m
Does this help?
http://stackoverflow.com/questions/20062197/how-to-disable-wal-journal-mode
On Apr 6, 2016, at 10:21 PM, Jerry Krinock wrote:
>
>> On 2016 Apr 06, at 08:27, Jens Alfke wrote:
>>
>> If you’re seeing high memory utilization, it’s more likely something to do
>> with Core Data i
Hi all,
My app uses [NSWorkspace openURL:] to display help pages in the user’s default
browser. Each new request creates a new tab (at least in Safari). Is there a
way to pass a hint that no new tab is created if there is an existing tab for
the same domain? I looked at NSWorkspace’s launch opt
> On 2016 Apr 06, at 08:27, Jens Alfke wrote:
>
> If you’re seeing high memory utilization, it’s more likely something to do
> with Core Data itself. It might be a symptom of a way you’re misusing Core
> Data
I agree, having had an experience like James’ last year. It is a huge project;
the
On Feb 26, 2016, at 6:12 PM, Jens Alfke wrote:
> On Feb 26, 2016, at 4:48 PM, Quincey Morris
> wrote:
>>
>> According to NSError documentation:
>
> Thanks, but I did read the documentation before asking.
I think Quincey Morris' summary is accurate - at least, it matches my
understanding - a
> On Apr 6, 2016, at 8:45 AM, James Cicenia wrote:
>
> This is only at the install. The WAL file grows to over 500MB. Then when the
> app is restarted this WAL file is truncated and app goes down to about 35MB.
Oh, you mean _disk_ storage. I thought you meant RAM.
Looking through the WAL docs
This is only at the install. The WAL file grows to over 500MB. Then when the
app is restarted this WAL file is truncated and app goes down to about 35MB.
I don’t know enough about sqlite and how it will handle the situation of when
there is only 400MB left on the device.
Basically I am using Re
> On Apr 6, 2016, at 7:43 AM, James Cicenia wrote:
>
> What is the magic combination of options to send to the sqlite to completely
> turn off journaling.
> I have an initialization on install that brings down a lot of data. I don’t
> need journaling at this point
> and it balloons the memory
What is the magic combination of options to send to the sqlite to completely
turn off journaling.
I have an initialization on install that brings down a lot of data. I don’t
need journaling at this point
and it balloons the memory storage upon install to over 500MB!
I have tried:
var options
I’ve been filing radars and complaining about this for almost 3 years now
(since iOS7). So far the only way to detect if a hardware keyboard is present
is through private APIs (and those only if a text view on text field is
currently the first responder).
If anyone has a good solution, I’d be h
If not there already, it seems like this type of functionality needs to be
on the critical path ... or someone's radar?
How does one take advantage of the screen if there is no authoritative way
to determine if the keyboard is covering half of it? Especially since the
pro's case now comes with a b
11 matches
Mail list logo
