Re: AS, wIP and 10.4.3: nothing's changed...
Re: AS, wIP and 10.4.3: nothing's changed...
- Subject: Re: AS, wIP and 10.4.3: nothing's changed...
- From: Emile Schwarz <email@hidden>
- Date: Wed, 02 Nov 2005 20:47:27 +0100
Hi all,
{Dave, this is not a personal attack and I thank you for your involvment and
answer on this matter}.
Fortunately for me, I do not earn money for what I do with AppleScript.
Unfortunately - still for me - I can't use Tiger. The below discussion is just
one case, I have some more.
Also, for unknown reason, in early september 2005, I lost a folder contents [I
was using Tiger since April 29th, 2005] and was very upset because of that (the
PowerBook 15" Alu had 13 month to buy date). *
Even the Apple Tool (in fact not the Apple tool) wasn't able to repair the
trouble [the Apple Care tool]. :(
At last, I used this opportunity (bad opportunity) to copy the hard disk
contents to elsewhere (some DVD-RW... slow, very slow), format it and install...
Mac OS X 10.3 and update it to 10.3.9 (with all mini-updates, now, it is a real
shame).
I use it since then.
I loose my way since I started this message. I go back to the core of the
subject: Mac OS X 10.4.3 is not rock solid (and is far from that).
"If I knew that before buying the Tiger, I would not waste my money"...
Unfortunately, it is not possible in France to get my money back (I already
removed Mac OS X 10.4.2 from my internal hard drive).
A REAL SHAME: a whole OS who will not be updated to give what the previous
version (10.3) was able to give.
You do not have an idea of how I am furious...
Snap to grid does not works ! [I checked on some friend who use a TiBook and
have updated his OS]
I do not liked to wrote some month ago that Tiger is the worst Apple Operating
System I ever saw since I buy my first Apple Computer back in 1985, but this is
another evidence that this is not really an engineer bug, but a Design
Intelligence decision.
As a developer, I understand that bugs are not added voluntaree by the
developer, but instead the result of some special event. Bug are very hard to
find, less hard to remove. But when the but have been removed and not given to
the users, it is not only a shame but a real offence to all the people who use
this software (Operating System in this case).
There must be an entry in the Patriot Act against those cases.
One more time, I present my sincere apologies to the Apple developers who work
hard everyday to make Mac OS X getting better.
And to the guy who is in the dark side and decide to not include this kind of
bug removals in the OS to think twice, it is not alright. Please, come back to
the light side; come back home, remember: "The power to do your best".
Users, think that if this bug removal is not given to us, what other bug squash
was not implemented in 10.4.3 ?[will not be implemented in the future ?]
The poet wrote and sang: "The Times They Are A Changin'". Unfortunately, it is
not for the best :(
Regards,
Emile
PS: the given work around is good to have, but there are other nasty things that
happens and that does not have any work-arounds.
PPS: The only thing that I miss - after two month of use of Mac OS X 10.3.9 - is
... the English Dictionary.
Doh ! BTW: why don't we have a Spanish (I do not need it but some people in the
domestic market need it) or a French (Yes, Yes, Please Mr. Apple, give us a
French dictionary) dictionary ?
email@hidden wrote:
Date: Tue, 1 Nov 2005 14:50:30 -0800
From: Dave Lyons <email@hidden>
Subject: Re: AS, wIP and 10.4.3: nothing's changed...
To: Eugenio MORASSI <email@hidden>
Cc: email@hidden
Message-ID: <email@hidden>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
As usual from 10.4 till today's 10.4.3 update, Apple was (it seems)
not able to solve the problem I've already described here:
The main problem is that setting the "bounds" or "position" of a
Finder window from AppleScript doesn't make the change "stick." This
bug is fixed for a *future* version of Finder, but it is very
unlikely to be fixed in any 10.4.x version.
However, there is a way to work around the problem by changing the
script. After setting the position or bounds of the window, change
the window's toolbar visible setting, and then change it back:
tell application "Finder"
set position of Finder window 1 to {2, 49}
set toolbar visible of Finder window 1 to not toolbar visible of
Finder window 1
set toolbar visible of Finder window 1 to not toolbar visible of
Finder window 1
end tell
The temporary change will, unfortunately, be visible to the
user...but at least it works.
In this case, there is no need for an additional Radar bug, but in
general I agree exactly with what Yvan KOENIG wrote: Always file a
Radar bug (at <http://bugreport.apple.com>, for example). Please
don't assume that just describing a problem on a mailing list is good
enough to get it fixed.
* Nothing wrong appeared until I reboot the PowerBook on that early morning on
September 8th (2005, sunny day)... the Finder was searching... rainbow cursor,
trying to open that folder.
The AppleCare tool ran during 8 hours (9:00 'till 17:00) until it told me what
happens: I can't repair one volume information block folder entry so make a back
up of your data, format the hard disk and re-install the OS :(
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden