Re: Appleworks bug and possible workarounds
Re: Appleworks bug and possible workarounds
- Subject: Re: Appleworks bug and possible workarounds
- From: Harald E Brandt <email@hidden>
- Date: Sat, 17 Apr 2004 16:22:48 +0200
Users said:
Brennan:
The trouble with Appleworks is that the scripting implementation is so
broken that you can barely get started. If Apple is expecting bug
reports,
all they can hope to get is 'pretty much everything screws up'.
Appleworks
isn't even mentioned in the bug reporter 'product/component' popup
menu.
and...
Bill:
I've had a look in the list archives and there's nothing about this.
Looks like few people even bother to script AppleWorks. Not much
wonder.
I have done quite involved and intricate scripts with AppleWorks
Spreadsheets.
Unfortunately, I agree with both of you!...
I did all that scripting of AW in an attempt to stay "Microsoft-free",
but I think I regret it.
Of all the nasty AW bugs, I only bothered to report one -- a really
nasty bug that crashed the whole AW! That was back in 2002! But the
report is still in an "open/analyze" state (and the very simple
property statement still crashes AW). So, unfortunately, I think that
is a sign it has close to zero priority.
I also had to revert to crude 'paste' of stuff since it was completely
impossible to solve it any other way - not really what you would expect
of something "scriptable".
I regret I started with AW Spreadsheets back then.
(I believe the database part is a lot better though)
--heb
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.