Moderators: Eyal Redler, redlers, Ori Redler
When you perform a forced quit, I think you get a crash log.JFM wrote:I could indeed report all of this to the Redlers. If I could send them however some report about what is happening, it would probably be helpful to them. Do you have any idea about some log which might contain a lead?
Right - and indeed, Mellel seems to be the only application having any problem, all other applications are working fine.miles11 wrote:I've read this entire thread and it sounds like your problem is application specific (Mellel is the only problem). That is, it sounds like your other apps are working fine, is that so? If so, that would seem to eliminate your hard drive as the culprit.
One thing I noticed is that you didn't mention checking your preferences file. Is it possible that something as simple as a corrupted preference file would cause this?
User>Library>Preferences>com.redlex.mellel.plist
You can easily pull that file to the desktop, quit Mellel, then relaunch it. It would create a new preference file, and Mellel should work properly—IF that is your problem.
Just trying to cover all bases. It usually makes sense to try all the quick, simple things first.
—miles
Grasping at straws here:JFM wrote:I don't understand. There must be a very simple solution. But what?
As it seems to be a software problem, maybe the content of some Mellel Documents cause Mellel to hang while trying to open a document. The “content” could be a lot of things, for example text/images, text with some fonts, text using some hyphenation-dictionaries, text using some styles/style-sets, text using some auto-title setups (where the images/fonts/styles/auto-title setups/hyphenation-dictionaries could cause your problems)JFM wrote: However, the system obviously notices something goes wrong: if I go in the Apple "Forcequit" menu, shortly after I attempt to open one of the documents, there is the red warning "does not reply" next to Mellel. And the only way to quit Mellel is to forcequit.
Still, there are three Mellel documents which continue to open without any problem on my iBook. This is what really puzzles me: if the problem would be with all Mellel documents - but why are a few exempt from the problem?
In general, the compressed files are a lot of smaller so that’s the suggested option to select. In the past, some users had problems with compressed files, as the used compression library (a part of Mac OS) didn’t work for all users. So I suggested to turn of compression to see if the compression library is the troublemaker.JFM wrote: By the way, since you seem well-informed about that, what are the advantages or inconvenience of having/not having the compressed file format?
Neither the age nor the free space guarantees a perfect running system. For example, the HD in my sister’s one year old MacBook died some weeks ago and the first thing she noticed were some Pages documents that refused to open so Pages looked like the bad man at first. As those documents couldn’t be opened on any other system and shortly after some other files couldn’t be opened/saved the real troublemaker became visible. I don’t think that you have the same problem, I only liked to explain, why a faulty HD could make an application look broken.JFM wrote:Hardware failure... yes, maybe, but it is difficult to understand why the problem is only with Mellel. And my iBook hard disk is not overloaded, since the original one was replaced with a new, larger one two years ago - I use less than half the total disk space.
