Linkback
I'm at a complete loss now. It will be interesting to see if Nisus support is able to add any more to this one. I agree the test account would be an interesting avenue to pursue but it seems like a lot of work. I've killed all the weird apps to see if one of them is clashing, the app would remain the same and only the prefs would be clean(?)
SteveH, when you double click on the OG graphic in NWX is OG still active? I seem to recall someone else having a similar problem with LinkBack a while ago (can't find the thread now alas). As I recall they found that if they kept the app being linked to from NWX (e.g. OG) in memory it worked, but linking to another app from NWX using LB wouldn't launch the other app for some reason.
I don't know if this was ever really explained but it sounds like it might be a permissions/ownership problem for the two executables. Maybe one is installed/owned by an Admin user (in /Applications) and the other by a non-Admin user in /Users/<non-admin-user>/Applications or something? I don't know about OG but NWX can be installed either way - executable by any user on the machine or just a particular user (in which case I think it's installed in ~/Applications rather than /Applications and it's permissions are set to make it executable only by that user.)
I don't know if this was ever really explained but it sounds like it might be a permissions/ownership problem for the two executables. Maybe one is installed/owned by an Admin user (in /Applications) and the other by a non-Admin user in /Users/<non-admin-user>/Applications or something? I don't know about OG but NWX can be installed either way - executable by any user on the machine or just a particular user (in which case I think it's installed in ~/Applications rather than /Applications and it's permissions are set to make it executable only by that user.)
I tried this and got some results but they need expert interpretation to see if they are relevant.
The following is taken from the console.log when starting up a Nisus document with a OG graphic. I also get the same thing when opening a regular RTF file with no graphics.
There was nothing recorded in system.log and neither log generated anything when the app beachballed after double-clicking a graphic.
The following is taken from the console.log when starting up a Nisus document with a OG graphic. I also get the same thing when opening a regular RTF file with no graphics.
Code: Select all
===== Wednesday, 7 December 2005 20:11:18 Europe/London =====
2005-12-07 20:11:39.289 Nisus Writer Express[750] .scriptSuite warning for attribute 'selectedText' of class 'NWDocument' in suite 'NisusWriter': 'NSTextStorage' is not a valid type name.
Linkback Failure
Yeah, I get the same console message when I launch NWX, no opening of any document required. I don't think it's anything significant and apparently unrelated to your LB problem. The fact that you get no messages when double-clicking on the OG graphic in NWX is the key, if disappointing, result. I'm sorry but I can't think of anything else you can try, I think Nisus support will have to crack this one.
Linkback with 2.6
I've just downloaded NWE 2.6 this morning and tried my usual Linkback test with an embedded OmniGraffle diagram. Again, I am unable to edit the embedded image - not a great surprise to me as I tried FC2 last week and found the same. I am now running latest version of OS 10.4, Omnigraffle and NWE.
What does surprise me is that despite five emails to Nisus on this subject since I registered in mid-November, I have not a had any official response to my support request. Nothing.
I am pretty disappointed, as Linkback was one of the main reasons for choosing to use NWE as I frequently need to create technical specs and it is useful to be able to work from within one document.
What does surprise me is that despite five emails to Nisus on this subject since I registered in mid-November, I have not a had any official response to my support request. Nothing.
I am pretty disappointed, as Linkback was one of the main reasons for choosing to use NWE as I frequently need to create technical specs and it is useful to be able to work from within one document.