|
Re: How to return data for NXSMLParserDelegate's -parser:resolveExternalEntityName:systemID:
Same error. Thanks for the suggestion.
--
Steve Mills
Drummer, Mac geek
Same error. Thanks for the suggestion.
--
Steve Mills
Drummer, Mac geek
|
By
Steve Mills
·
#1124
·
|
|
Re: How to return data for NXSMLParserDelegate's -parser:resolveExternalEntityName:systemID:
Have you tried returning a full XML entity, e.g. "<string> </string>"?
That would be my next experiment...
--
Glenn L. Austin, Computer Wizard and Race Car Driver
Have you tried returning a full XML entity, e.g. "<string> </string>"?
That would be my next experiment...
--
Glenn L. Austin, Computer Wizard and Race Car Driver
|
By
Glenn L. Austin
·
#1123
·
|
|
How to return data for NXSMLParserDelegate's -parser:resolveExternalEntityName:systemID:
What is the expected value of the returned NSData supposed to be for this method? The docs says "An NSData object that contains the resolution of the given external entity." To me, that means that for
What is the expected value of the returned NSData supposed to be for this method? The docs says "An NSData object that contains the resolution of the given external entity." To me, that means that for
|
By
Steve Mills
·
#1122
·
|
|
Re: Crash in Apple code, not mine - what can I do?
Ugh - I don't have a whole lot of experience with CoreData, but it does add a whole lot of possible failure modes. It's tough that you can't reproduce the issue locally - any chance the customer will
Ugh - I don't have a whole lot of experience with CoreData, but it does add a whole lot of possible failure modes. It's tough that you can't reproduce the issue locally - any chance the customer will
|
By
Jon Gotow
·
#1121
·
|
|
Re: Crash in Apple code, not mine - what can I do?
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00006db9f91b0e58
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00006db9f91b0e58
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault:
|
By
Steve Mills
·
#1120
·
|
|
Re: Crash in Apple code, not mine - what can I do?
What's the actual cause of the crash? A segmentation fault (SIGSEGV) or some other memory error could be caused by you corrupting memory, handing NSDocumentController a bad object somehow, or some
What's the actual cause of the crash? A segmentation fault (SIGSEGV) or some other memory error could be caused by you corrupting memory, handing NSDocumentController a bad object somehow, or some
|
By
Jon Gotow
·
#1119
·
|
|
Crash in Apple code, not mine - what can I do?
A customer sent a crashlog that clearly shows Apple's code is what's crashing on 10.14.6. There's no way I can reproduce it. So what can I do? Just submit a bug to Apple with the crashlog (although
A customer sent a crashlog that clearly shows Apple's code is what's crashing on 10.14.6. There's no way I can reproduce it. So what can I do? Just submit a bug to Apple with the crashlog (although
|
By
Steve Mills
·
#1118
·
|
|
Playing a sequence of notes with AVAudioSourceNode
Is it possible to set up an AVAudioEngine and friends so I could feed it a sequence of MIDI notes and have it play that sequence, using an AVAudioSourceNode as the sound source? The AVAudioSourceNode
Is it possible to set up an AVAudioEngine and friends so I could feed it a sequence of MIDI notes and have it play that sequence, using an AVAudioSourceNode as the sound source? The AVAudioSourceNode
|
By
Steve Mills
·
#1117
·
|
|
Re: Parsing Javascript simply
We use a WebView/WKWebView for accessing web page DOMs using xPath queries. We used to be able to even interact with Java Applets, but security improvements have killed that functionality after 10.6.
We use a WebView/WKWebView for accessing web page DOMs using xPath queries. We used to be able to even interact with Java Applets, but security improvements have killed that functionality after 10.6.
|
By
Sandor Szatmari
·
#1116
·
|
|
Re: Parsing Javascript simply
Thanks - indeed simple to try, but unfortunately doesn’t work in this case.
I’ll try loading it into an off-screen WKWebView.
—Graham
Thanks - indeed simple to try, but unfortunately doesn’t work in this case.
I’ll try loading it into an off-screen WKWebView.
—Graham
|
By
Graham Cox
·
#1115
·
|
|
Re: Parsing Javascript simply
Did you try loading the page in a WebView? Then you should be able to traverse the DOM.
Sandor
Did you try loading the page in a WebView? Then you should be able to traverse the DOM.
Sandor
|
By
Sandor Szatmari
·
#1114
·
|
|
Re: Parsing Javascript simply
I tried something similar recently, and got better-than-anticipated results using this NSAttributedString
I tried something similar recently, and got better-than-anticipated results using this NSAttributedString
|
By
Quincey Morris
·
#1113
·
|
|
Parsing Javascript simply
Hi all,
I made an app that scrapes web pages looking for a specific tag - namely, the <video> tag to get the address of a video stream. If you display the page in e.g Safari, the video portion can be
Hi all,
I made an app that scrapes web pages looking for a specific tag - namely, the <video> tag to get the address of a video stream. If you display the page in e.g Safari, the video portion can be
|
By
Graham Cox
·
#1112
·
|
|
Re: Advice on implementing a URL Text Field
Have you turned on the data detectors options available in text views? That might be enough unless you’re seeing something it doesn’t give you.
--
Gary L. Wade
http://www.garywade.com/
Have you turned on the data detectors options available in text views? That might be enough unless you’re seeing something it doesn’t give you.
--
Gary L. Wade
http://www.garywade.com/
|
By
Gary L. Wade
·
#1111
·
|
|
Advice on implementing a URL Text Field
I am looking for some advice and/or suggestions on implementing an iOS text field with the following properties:
The user can enter text into the field easily (via keyboard, pasting, etc).
If the
I am looking for some advice and/or suggestions on implementing an iOS text field with the following properties:
The user can enter text into the field easily (via keyboard, pasting, etc).
If the
|
By
Rick Aurbach
·
#1110
·
|
|
Re: NSAttributedString + NSLayoutManager versus Core Text
I haven’t done this with CoreText personally, but you need to traverse the runs yourself to know where the characters are rather than rely on callbacks. What code do you use for the CoreText
I haven’t done this with CoreText personally, but you need to traverse the runs yourself to know where the characters are rather than rely on callbacks. What code do you use for the CoreText
|
By
Gary L. Wade
·
#1109
·
|
|
Re: Weird crash with Mojave, no crash on High Sierra
I trust it is a Mac app?
What is the crash log?
I trust it is a Mac app?
What is the crash log?
|
By
Alex Zavatone
·
#1108
·
|
|
Re: Weird crash with Mojave, no crash on High Sierra
Thanks a lot, seems to have cured things. I added a line to set the window delegate to nil before [myWindow close] and things are ok now.
---markus---
Thanks a lot, seems to have cured things. I added a line to set the window delegate to nil before [myWindow close] and things are ok now.
---markus---
|
By
Markus Ruggiero
·
#1107
·
|
|
Re: manual item enabling
Kurt,
The menu key equivalents are pulled out before -keyDown: is called. You can override that event in -performKeyEquivalent:, a methof of NSResponder (and therefore views, etc). You can probably
Kurt,
The menu key equivalents are pulled out before -keyDown: is called. You can override that event in -performKeyEquivalent:, a methof of NSResponder (and therefore views, etc). You can probably
|
By
Graham Cox
·
#1106
·
|
|
Anyone know what this means?
Sometimes I get the following message logged when by app quits:
*** _NSDocumentBasicAsyncOperation 0x600003e25a00 went isFinished=YES without being started by the queue it is in
It seems to be
Sometimes I get the following message logged when by app quits:
*** _NSDocumentBasicAsyncOperation 0x600003e25a00 went isFinished=YES without being started by the queue it is in
It seems to be
|
By
Graham Cox
·
#1105
·
|