> On 2017 Apr 24, at 18:29, Frank D. Engel, Jr. wrote:
>
> At this point, since it is really only one of these anchors to a page of help
> anyway, I am thinking I will rework to name the files what I was previously
> calling the anchors and just open the online help in a web browser, maybe an
> On 27 Apr 2017, at 23:44, Quincey Morris
> wrote:
>
>> On Apr 27, 2017, at 15:27 , Peter Hudson wrote:
>>
>> This is a document based app.
>> And it's the same table view that is affected each time. […] And I find it
>> strange that the table view address should become exactly the same
On Apr 27, 2017, at 15:27 , Peter Hudson wrote:
>
> This is a document based app.
> And it's the same table view that is affected each time. […] And I find it
> strange that the table view address should become exactly the same as it had
> in a previous document that has been closed.
I’m sor
Hi Quincey
This is a document based app.
And it's the same table view that is affected each time. I doubt it's a hidden
UI element issue.
I'll have a look around the dangling pointer area.
All strange as the code involved has been running happily for a long time and
is quite straightforwar
On Apr 27, 2017, at 13:26 , Peter Hudson wrote:
>
> I open I file in my application, do a few typical operations in it - and then
> shut the file.
I assume you mean this is a data file whose contents are displayed (for the
moment) in your UI, not an actual NIB file containing a table view?
>
macOS 10.12.3 Xcode 8.3
I have a very strange problem I have never come across before.
I open I file in my application, do a few typical operations in it - and then
shut the file.
I then open another file - and do a few typical operations in it.
The app then grinds to a halt with an illega
