On 21 Oct 2013, at 06:01, Seth Willits wrote:
> On Oct 19, 2013, at 9:27 AM, Jerry Krinock wrote:
>
>> That's interesting and I've never seen it done.
>>
>> I'd call it a variation of writing custom accessors for each attribute.
>> Custom accessors for each attribute have the advantage of rel
>> Why don't you want to bind the Selected Index? It does what you want.
>>
> Because I don't want the menu to reflect the selection in the table. I just
> need the contents of the menu to match the contents of the table, but the
> selections in each place need to be independent of each other.
>
Hi,
I have a custom subclass of NSTableView in my app.
I would like to change the highlight colour displayed when the user clicks on a
row, and have the colour maintained when the NSTableView subclass loses focus.
I have changed the subclass to ensure that the table is never first responder,
a
On 21 Oct 2013, at 16:19, Darren Wheatley wrote:
> Hi,
>
> I have a custom subclass of NSTableView in my app.
>
> Can anyone suggest a method that will allow me to set a custom highlight
> colour on on a row when the user clicks on it?
>
> I've Googled for a solution, but haven't been able to
On Oct 21, 2013, at 3:58 AM, jonat...@mugginsoft.com wrote:
> Yes. You need to keep your wits about you with this sort of thing.
>
>> I gag a little whenever I remember that's how it works, but at this point it
>> ain't broke so I'm not going to tempt fate by fixing it. ;-)
>>
> What would you
I'm considering to add some functionality to my app from a 3rd party open
source project. I've compiled the program with homebrew and copied the bin
files into my Xcode project. I looked into NSTask, but that is not available
for iOS.
Is it possible to do this?
Thanks,
- Koen.
On Oct 21, 2013, at 11:04 AM, Koen van der Drift
wrote:
> I'm considering to add some functionality to my app from a 3rd party open
> source project.
What’s the project?
> I've compiled the program with homebrew and copied the bin files into my
> Xcode project. I looked into NSTask, but th
On Oct 21, 2013, at 2:43 PM, Jens Alfke wrote:
> Can you configure that project as a [static] library that you can link into
> your app and call directly?
Yeah, I though about that as well, and am going to try that. It comes with
makefiles for Mac (OSX only though), so I'll start with that.
I’ve just gotten a nasty bug report involving an iOS app hanging when it goes
into the background. The problem is a deadlock involving NSCache. I can see
what the problem is, but I don’t know what to do about it.
In a nutshell: An NSCache is evicting objects, and as a result of that its last
re
On Oct 21, 2013, at 2:11 PM, Jens Alfke wrote:
> Specifically, there is a “database” object that has a strong reference to an
> NSCache which maps to various ‘document’ objects (indexed by key.) The
> document objects have strong references back to the database.
>
> In the situation that hangs,
I think I am on the right track now. I'm building the project (plain c) on the
command line with an updated makefile for iOS, but am getting some compiler and
linker errors. Since this is outside the scope of this mailing list I will ask
additional questions on the Xcode list.
- Koen.
On Oc
After modifying a Core Data document-based OS X app, it no longer autosaves
when quit. I need to fix that so it autosaves again.
Because my app is unfortunately complicated, I'm instead trying to understand
how autosave works when quitting a normal app. Here is what I did:
• Get Apple Sampl
On Oct 21, 2013, at 3:38 PM, Jerry Krinock wrote:
> • There is another issue, beside the fact that saving does not occur: The app
> does not quit either. But neither does it hang. It does quit if I command
> it to quit a second time (with no changes).
> • During that first failed quit, -[NSApp
On 2013 Oct 21, at 14:08, Ken Thomases wrote:
> This sounds like an exception was raised during the processing of the first
> quit. Have you checked the console output? Do you have a breakpoint on
> Objective-C exceptions?
Good thinking as usual, Ken, but unfortunately the answers are YES.
I still don't know what's wrong or how to fix it, but I think the problem
probably stems from the fact that I have designed this app to have a single
"shoebox" document. The app quits when this document closes. It looks like
the closing and quitting methods are stepping into or onto one anot
Hello Noah and others,
I have been looking for databases with optimistic transaction control for use
with Core Data Persistent Store for ODBC. I found only one such database, the
swedish Mimer. All the big names like IBM DB2, MySQL, Oracle and SQL Server use
locking. Do you know any other datab
On Oct 21, 2013, at 4:39 PM, Jerry Krinock wrote:
> It looks like the closing and quitting methods are stepping into or onto one
> another somehow.
All the interactions here are subtle and thinly documented. It all "just works"
for standard document-based apps and subclasses of NSDocument, bu
On 2013 Oct 21, at 16:23, Scott Ribe wrote:
> All the interactions here are subtle and thinly documented. It all "just
> works" for standard document-based apps and subclasses of NSDocument, but
> once you step outside that realm it can be tricky to get everything to work
> right.
Thank you,
Ok, I figured it out. I was able to build three different static libraries for
armv7, armv7s and i386 and combined them with lipo into one that I added to my
project.
The question now is, how do I call the functions in this library?
On the command line, I need to do something like this:
foo fi
Import the headers and call the functions, if you're linking your application
against it.
Daniel
On Oct 21, 2013, at 6:26 PM, Koen van der Drift
wrote:
> Ok, I figured it out. I was able to build three different static libraries
> for armv7, armv7s and i386 and combined them with lipo into
Can you just manually retain it before cleaning, and manually release it
afterwards? You can use CFRetain()/CFRelease() for that, or use runtime
functions objc_retain() and objc_release(). The latter two is not documented by
Apple per sé, but it is documented by LLVM as requirements of ARC.
Sen
Despite NSTask is missing in runtime, your day can still be saved by:
1) You can use the NSTask implementation from GNUstep, an LGPL-licensed library.
2) You can still use classic UNIX function calls to pipe/fork/dup2/exec
Sent from my iPhone
> On 2013年10月22日, at 9:37, Daniel DeCovnick wrote:
>
No fork() on iOS and the GNUStep version of NSTask uses fork(), so that's not
going to work.
Apart from that, if you've built the library, you just call the functions.
On 22 Oct, 2013, at 10:02 am, ChanMaxthon wrote:
> Despite NSTask is missing in runtime, your day can still be saved by:
>
On Oct 21, 2013, at 10:12 PM, Roland King wrote:
> No fork() on iOS and the GNUStep version of NSTask uses fork(), so that's not
> going to work.
>
> Apart from that, if you've built the library, you just call the functions.
Actually, the library doesn't create functions, just executable bi
On Oct 21, 2013, at 6:57 PM, ChanMaxthon wrote:
> Can you just manually retain it before cleaning, and manually release it
> afterwards? You can use CFRetain()/CFRelease() for that, or use runtime
> functions objc_retain() and objc_release(). The latter two is not documented
> by Apple per sé
If you can understand the code, just read it and make it a library.
Else, you need an alternative. Try research on how iSSH work. (They have a
separate PuTTY executable, due to license issues)
On Oct 22, 2013, at 10:52, Koen van der Drift wrote:
>
> On Oct 21, 2013, at 10:12 PM, Roland King
On Oct 21, 2013, at 7:02 PM, ChanMaxthon wrote:
> 2) You can still use classic UNIX function calls to pipe/fork/dup2/exec
I think this is another of those “…ok, only if you jailbreak your device or
maybe if you’re building an enterprise-only app” things, right? You should
really make that cle
What about the “database” object? Is that yours? If so, can you
retain/autorelease it (using runtime functions documented by LLVM) when purging?
On Oct 22, 2013, at 10:53, Jens Alfke wrote:
>
> On Oct 21, 2013, at 6:57 PM, ChanMaxthon wrote:
>
>> Can you just manually retain it before cleani
On Oct 21, 2013, at 6:26 PM, Koen van der Drift
wrote:
> The question now is, how do I call the functions in this library?
> On the command line, I need to do something like this:
> foo file1 > output
> With NSTask and companions it is easy to do this, but how can I do that for
> iOS where NST
No, this pipe/fork/dup2/exec is used in App Store apps - iSSH is an example as
it used its separate PuTTY executable. Maybe straight fork() is not available
but is there some replacement like posix_spawn()? iOS itself need some sort of
mechanism to fork/exec or there will be no apps.
On Oct 22,
On Oct 21, 2013, at 7:57 PM, Maxthon Chan wrote:
> What about the “database” object? Is that yours? If so, can you
> retain/autorelease it (using runtime functions documented by LLVM) when
> purging?
Let me copy and paste what I said before: "I’m not in control of the cache
purge — it seems
If your app is called Hammersmith, you can retain/autorelease it in your
[CBLDatabase dealloc] or [CBLCache dealloc]
On Oct 22, 2013, at 11:03, Jens Alfke wrote:
>
> On Oct 21, 2013, at 7:57 PM, Maxthon Chan wrote:
>
>> What about the “database” object? Is that yours? If so, can you
>> reta
On Oct 21, 2013, at 12:28 PM, Ken Thomases wrote:
> Seems like a cycle to me. … Have the documents hold weak references to the
> database.
Agreed.
What reason is there for the documents to have a strong reference to the
database?
--
Seth Willits
On Oct 21, 2013, at 20:02, Maxthon Chan wrote:
> No, this pipe/fork/dup2/exec is used in App Store apps -
No. I am sorry, but you are wrong.
> iSSH is an example as it used its separate PuTTY executable.
iSSH does not use a separate executable. It is not possible to do so from a 3rd
party iO
I stand corrected - iOS fork() refuses to work.
On Oct 22, 2013, at 11:59, Clark S. Cox III wrote:
>
> On Oct 21, 2013, at 20:02, Maxthon Chan wrote:
>
>> No, this pipe/fork/dup2/exec is used in App Store apps -
>
> No. I am sorry, but you are wrong.
>
>> iSSH is an example as it used its s
On Oct 21, 2013, at 8:07 PM, Maxthon Chan wrote:
> If your app is called Hammersmith, you can retain/autorelease it in your
> [CBLDatabase dealloc] or [CBLCache dealloc]
It’s not my app, it’s a customer’s that uses my library. But the CBL classes
are part of my library, yes.
As for autorelea
Well you can read GNUstep’s objc-arc.h (in libobjc2) to get some idea on
LLVM-defined runtime functions that is required to make ARC work. There are
functions objc_retain and objc_autorelease (Using those will not get you
rejected - apple cannot tell your manual calls from calls generated by
co
On Oct 21, 2013, at 8:09 PM, Seth Willits wrote:
> What reason is there for the documents to have a strong reference to the
> database?
The database object has all the core functionality including the underlying
data storage engine. The document calls into the database to do the real work
li
Sent pull request.
https://github.com/couchbase/couchbase-lite-ios/pull/165
On Oct 22, 2013, at 13:14, Jens Alfke wrote:
>
> On Oct 21, 2013, at 8:07 PM, Maxthon Chan wrote:
>
>> If your app is called Hammersmith, you can retain/autorelease it in your
>> [CBLDatabase dealloc] or [CBLCache d
I am trying to convert this to Arc:
- (BOOL)doSomethingWithSelector: (SEL)aSelector
{
[...]
NSNumber *status = [ self performSelector: aSelector withObject: a
withObject: b ];
[...]
}
Xcode 5.0 complains: "PerformSelector may cause a leak because its selector is
unkn
You can tell it to ignore the warning like this:
#pragma clang diagnostic push
#pragma clang diagnostic ignored "-Warc-performSelector-leaks"
NSNumber *status = [ self performSelector: aSelector withObject: a
withObject: b ];
#pragma clang diagnostic pop
Hope that helps.
Gideon
On 22
41 matches
Mail list logo
