DJ, what if they REMOVED an icon you're relying on ?

I was already against displaying the status area before. Now it HAS to be hidden.

But if you're building your own mono-user little DVD library (I doubt I would choose FileMaker to do so), then the new toolbar is not dangerous... only ugly :

DJ, what if they REMOVED an icon you're relying on ?

Then you have a poorly designed interface.

Users expect to be able to interface with an app in multiple ways (drop down menu/toolbar/shortcut key) when performing basic functions.

I wouldn't put the control for a basic function solely on a tool bar.

I wouldn't either, but before there was no way the status area could disable a feature, that's what I meant. And one could think 'now that I have this toolbar, let's rely on it for my UI'

Edited January 9, 200917 yr by Guest

In pre- 10 versions, there are a dozen ways an ignorant developer could shoot themselves in the foot using tools they don't fully understand.

I don't see how this change is any different.

I do think the script triggers are going to cause a lot more headaches from people over using them or not understanding exactly how they work though.

Ditto.

It's been interesting, watching the folks in our own shop come up with new ways to use script triggers - things I never would have thought of, which is great. I think out of the collective talent pool we're going to see some great uses that none of us individually can currently envision.

But, we're also going to see LOTS of misapplications, and folks getting themselves into heaps of trouble with this.

Is there a forum thread just for Script Triggers yet? Because we'll need one.

yep, just look above in the Next Level up.