MANFRED BERGMANN  Version 2.0.1 had a problem only on Leopard (10.5) systems. It wasn't possible to open a Workspace window.  
(Version 2.0.2-269)

SOUTHPAWAMI  Developer... I was figuring it was a 10.5 issue only. As 10.4 isn't supported anymore as far as I know. The prior macsword I was speaking of crashed after the update, then would not start. I had to go into Application Support through the Library to delete the MacSword folder before it would load up again. After that, it did start, the window just would not display. I deleted the Sword folder as well, but to no avail, it would simply start up and never display a window. I'm sure you've fixed the problem already, and I'll be downloading this version in a moment.  
(Version 2.0.2-269)

TOMEG  I have *never* gotten MacSword 2 to work. I first downloaded v. 2 beta longer than a year ago, having enjoyed using v. 1. I have installed updates to 2 as they have come along, hoping maybe I could get the app to open at some point in development. But, NO. Not once nor ever has it successfully opened. Instead, with each and every install, I have had exactly the same result: on first launch, the app icon bounces 3 or 4 times in the dock, then quits, I always get the standard system alert 'MacSword quit unexpectedly. Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.' When I click Reopen, again the app's icon appears in the dock momentarily, then disappears, and that's it.

I have tried everything I can think of, including: trash the app along with its associated files/folders on my hard drive, and Secure Empty Trash, then download move the app from my Downloads Folder to Applications, click to open the app afresh; and it crashes exactly the same as before. I have performed this ritual a great many times, same procedure each and every time an updated version has become available. Nada. Zip. No change.

Believe me, I have been thorough, dogged and determined to eventually conquer this problem, and have done everything I know, consulted with other users taking their advice when it seemed appropriate and safe to do so. I have used Easy Find to root out any and all associated files, etc., each time with success.

As if this weren't the full extent of it, a year ago I (coincidentally) bought a brand new 24" iMac 2.8 GHz 4 Gigs Ram (Max), with a brand new La Cie external hard drive (which works beautifully with Time Machine); OS 10.5 then Snow Leopard when it first came out, installed every Security Update and System Update as it was released - now 10.6.1. [Aside. Boy do I love Snow Leopard, like no other OS X version since 10.1.]

Obviously I'm missing something but I don't know and can't imagine what it might be.

I should have written this Troubleshoot in MacUpdate a long time ago, but, you know, I have faith that a capable sincere developer will eventually catch most if not all the problems, and fix them. I hope writing this will lead (or at least progress) to a solution for my problem.

But now I'm really stumped. (I hate to admit this, since half the fun of owning a Mac is getting more and more involved in the cause to keep Apple at the forefront, and hopefully assist others as I have so many times been assisted to my great pleasure and satisfaction.) And I need help again. I have faith I will get it, and blessings on this project no matter my difficulties.

Tom G  
(Version 2.0.2-271)

MANFRED BERGMANN  TOMEG.

Why do you not write to me directly or to our support forum or to our users mailing list?

A problem description and a crash reporter log and I most probably could have told you what the problem is and how to work around it.

The reason that I can't catch all issues simply is that some don't occur in every environment.

Since our resources in time and test machines is very, very limited this project, as all open source project lives from helping users. This help doesn't need to be in coding but can simply be issue reporting.  
(Version 2.0.2-271)

TOMEG  MANFRED:

With all respect, *I HAVE POSTED THE SAME ISSUE* (though I admit not as rich in historical data) to the crossforge forums). I'm sorry I did not use the crash reporter as you suggest; but, you see, since I could not get MacSword 2 to open in the first place - its crashing every time on launch I as I have described - I saw no crash reporter. I'm also sorry I did not write to you directly on the matter. I confess I really expected my problem would have surfaced long ago from other users experience, and the appropriate fix would have been made. It may sound like nothing other than magical thinking on my part, but, since the program is widely used and popular, and the issue so basic, and my own system setup unremarkable, I thought watchful waiting was the more prudent course of action. So, yes, it is my fault and I'm sorry if this has upset you so much. As to informing you personally at last, consider my previous post your reference to the issue I request help with.

It's not often I fall down in my responsibility as a very long-time Mac user and enthusiast, but a mistake it was and I've learned a valuable lesson. Thanks. Please tell me the most expedient way to allow you to reply to me personally. Sincerely, Tom  
(Version 2.0.2-271)

MANFRED BERGMANN  TOMEG.

I'm not upset.

I couldn't remember you posted this on the Crosswire forums already. Sorry for that.

If you remember that thread, just open it up again or create a new one and I'll try to hunt things down with you.

This issue has most probably to do with an old MacSword 1 module installation base which for some unknown reason crashes MacSword 2.

There are some reports of users for this but I'm just unable to reproduce this problem on my two test machines.  
(Version 2.0.2-271)

MANFRED BERGMANN  The application works on Snow Leopard as it does on Leopard.

Why do you say it doesn't work?

Providing only an application bundle is a normal case on Mac OSX systems.

There is no need for an installer. You just drag&drop it so somewhere, then it is installed.

The CrossWire pages are not updated because MacSword 2 is not officially released yet.

I agree that we need to update our wiki pages and such.

But simply put the resources are limited, our spare time is limited. This is an open source software and project. Jump in and update those FAQs or the wiki.

I don't understand what you write about the modules. If you don't know how to install modules that just write to our mailing list or our forum or actually there are enough forum posts which explain exactly how it works.  
(Version 2.0rc4-246)

MANFRED BERGMANN  As for what you say about the "Sword" folder and modules. Please have a look at our wiki page. Even though it is not up to date it explains how to install modules using the module installer.

http://www.crosswire.org/wiki/Frontends:MacSword  
(Version 2.0rc4-246)

MANFRED BERGMANN  Thanks I'll have a look at those issues.  
(Version 2.0rc4-246)

MANFRED BERGMANN  This all is possible.

Bookmark folders can be nested. Just click on a bookmark folder and create another folder in in.

In a Bible tab/window commentaries can be added using either context menu on a commentary module in module list, here choose "open in current view" or click on the "+" button in the bible view and add a commentary of your choice.

Doing this will split the view and the commentary is shown below the bible text. Now scrolling in the commentary gets verse synchronized with the bible view or vise versa so that you always see the commentary or commentaries (more commentaries can be added like this) to your current bible verse.  
(Version 2.0rc2-228)

MANFRED BERGMANN  In case with you mean "footnotes" "colourized commentaries" which appear as blue links in bible text then you just need to either open the "preview panel" or switch on "Show preview as tooltip" in preferences.

This will show footnotes, Strong's number explanations or linked bible verses in the preview window or as tooltip if you keep you mouse pointer 2 secs over the link.  
(Version 2.0rc2-228)

PHALERON  Thanks for your help, without which I wouldn't know it was there. The last feature I mentioned is still missing (?). Say I created comments to various verses and want to review them but cannot remember the actual verses to which they belong. How do I access them (the comments) without first navigating to the verse?  
(Version 2.0rc2-228)

JPW  A loving God does not "create cancer". Man has chosen to unleash cancer into the genetic pool by pissing therein, i.e., on a large scale by means of environmental degradation, on a smaller scale, by choosing to partake of such activities as cigarette smoking.  
(Version 2.0rc2-228)

MANFRED BERGMANN  This version should use the module base that is already installed.

Some reports came in that they had to remove their installed modules under:

/Users//Library/Application Support/Sword

and re-install them using the module installer that comes with the application.

BTW: the module installer works the same way as with MacSword 1.4.3.

The interface is simple to use. On the left you have your installed modules and bookmarks.

Double click on a module and it opens. You can check the context menu on most places for available functions.  
(Version 2.0rc1-225)

MANFRED BERGMANN  Our user and support forum can also be of help:

http://www.crosswire.org/forums/mvnforum/index  
(Version 2.0rc1-225)

MJKPHOTO  I figured it out. Modules installed. Thank you for the reply.

MacSword is a remarkable Bible Study program.  
(Version 2.0rc1-225)

MACUPDATE ADMIN  "I send the reports to Apple..."

You should not do that, Apple is not the developer of MacSword, you should send the reports to the developer.  
(Version 2.0b2)

LWIEDER  I would contact the developer directly, but I can't find a communication link, or an email address for the developer on MacUpdate, or on (so far as I can see) at MacSword.  
(Version 2.0b2)

MACUPDATE ADMIN  mbergmann@crosswire.org is the address we have for this developer.  
(Version 2.0b2)

MANFRED BERGMANN  Yes, feedback goes to me, not to Apple.

The crashlog that is part of the crash window can be included in the mail.

Manfred  
(Version 2.0b2)