|
|
Post by futurosity on Oct 28, 2005 23:45:34 GMT
I'm going through the tutorial file. At Step 5, I try to follow your instructions to edit the index card. When I triple-click to select it, Scrivener crashed. I restarted and now it works, so this is going to be hard to pinpoint. I can send you the crash.log if you want.
|
|
|
|
Post by KB on Oct 28, 2005 23:50:12 GMT
Yes, the crash log would be helpful, thanks. If you could also try to remember everything you did up to the crash and try to get it to crash again, that would be helpful. I just tried it and I can't recreate it yet... Ach.
Thanks,
Keith
|
|
amberv
Junior Member
Posts: 99
|
Post by amberv on Oct 29, 2005 4:26:02 GMT
I experienced the same crash. I can also reproduce it. Here are the steps required. At this point you may crash. If not, continue:You should crash at this point. If not, repeat the above three steps again.The crash definitely seems tied to triple-click to select all, but only in a separate window. I was able to triple-click multiple times in the standard binder editor with no crashes. Using Cmd-A to select all does not seem to trigger a crash. I will send the crash log if you need it, but since you should be able to reproduce it now, let me know if you need it. |
|
|
|
Post by KB on Oct 29, 2005 8:14:19 GMT
Excellent! Thank you. I can now reproduce the crash. As I know what sort of crash it is from the crash log, now that I can reproduce it, it shouldn't be too hard to fix. I'll hopefully post an updated beta over the next couple of days that addresses this.
Thanks again,
KB
|
|
kaed
New Member
Posts: 2
|
Post by kaed on Oct 29, 2005 14:36:33 GMT
This also happened to me, with the same steps involved.
|
|
|
|
Post by KB on Oct 29, 2005 14:42:29 GMT
I'm working on it now... It's *very* hard to track down. I can reproduce it, but debugging it is hell. I'll squash it, though...
|
|
annik
New Member
Posts: 24
|
Post by annik on Oct 31, 2005 5:29:49 GMT
This is a bit OT but perhaps folks here will enjoy the thought ...
Last week I *had* to use M$ Word for something in my Uni courses. Long story, but basically the program I'm in provided me the licenced Mac copy so I could "do" the assignments the same as everybody else (on their lab PCs). Since I'm registered as "special needs" and have my own Mac in class for this purpose, we all agreed that its silly for me to use the school lab when I've got my own machine with me at all times.
Anyhow ... we had a group project and the $#$$%#@ app was crashing itself every few minutes, and at one point every few seconds. Very annoying, but in several years of technical writing across nearly every platform known to humankind, I'm familiar with a lot of the 'typical' quirks of several common writing apps, and considered the particular issue that influenced the app crashing to be absolutely typical M$ on Mac.
But I just got to thinking ... it certainly *could* be a useful 'slacker' feature to have a set of commands/keystrokes/etc. that could cause app crashes on-demand ...
One reason I've always preferred to freelance for technical writing is that when my "brain is full" while working on a new piece of hardware/software, I really need to have some time away from it, preferably by literally sleeping on the problem. After a sleep, everything seems to click into place. *Before* the sleep, however, all the new info/specs/bugs/expectations are a complete jumble in my brain, and I'm reasonably certain anything I try to write at that point comes out like some sort of Latinised Sanskrit.
Freelancers can often beg off on a project for the day without major complications ... employees usually cannot. And while I suppose it's nice to get paid for doing nothing, I'd rather be not paid and get the brain-sleep I need so that the *next* day I can accomplish things efficiently.
Anyhow ... not that I'd actually *do* anything like that, LOL!, but it is a nifty idea to play with for a Nano character. :-D
|
|
