growler_south (
growler_south) wrote2005-06-28 12:46 pm
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
Stupid logic (programmers logic)
I can drop files onto Quicklaunch buttons, so why not taskbar buttons? And why the patronising admonishment instead of just DOING WHAT I WANT OR DOING NOTHING AT ALL?

-It must have been easier to code If(drop onto taskbar button) Then(display annoying and insulting window) than it would be to code If(drop onto taskbar button) then(open dropped item in application)
I could understand if it was an oversight, IE dropping files onto taskbar buttons did nothing at all. But someone thought about it and decided that their way was so good, it was to be the ONLY way.
Grrrr...

-It must have been easier to code If(drop onto taskbar button) Then(display annoying and insulting window) than it would be to code If(drop onto taskbar button) then(open dropped item in application)
I could understand if it was an oversight, IE dropping files onto taskbar buttons did nothing at all. But someone thought about it and decided that their way was so good, it was to be the ONLY way.
Grrrr...
no subject
no subject
Stupid programmers.
no subject
The icons on the Quick-Launch bar represent applications that aren't running. So dropping a file on them means "run this app with that file". Simple enough.
But a taskbar button represents a window, not an application. So does it mean that the file should replace whatever is in that window? Probably not. Should it cause a single-file-at-a-time app like Notepad to launch another copy of itself? Probably not.
The essential problem here is that the Windows UI design opted to manage windows, not applications. But what users really want to deal with is applications. It was, to my eyes, shortsighted and lazy. (Or necessary to avoid a lawsuit.) MacOS got it right.
no subject
I guess there are applications where dropping into different parts of the window result in different actions, and it could be unfortunate if a file got dropped into the wrong part of the program.
no subject
Donald A. Norman has some great books on the subject, and one of his rules of thumb is that if you have to add a written note to explain how to use something, it's designed wrong. This is a great example of that.
Eh-yup
Re: Eh-yup
(and its not like Macs are without their irritating my-way-or-the-highway UI quirks...)
Re: Eh-yup
They just want to keep it lookin' pretty.
$40k of software? Egads man, I hope that's work related! I can understand about the processing power though I suppose. I'm still not sure about Apple's move to using Intel chips in the future. The purist in me shivers while the geek in me wants the speed.
Re: Eh-yup
Maya Unlimited, a few evil plugins (Arete nature tools being the most expensive), a whole raft of Adobe products (ouch!), C++...
Re: Eh-yup
So maybe I shouldn't have had that extra beer at dinner...
no subject
tee-hee, he said testi
The testee (http://www.testyfesty.com/) is tested in three catagories: Word, Powerpoint & Excel.
To frame, properly, my point, I gotta tell you that prior to preparing for the test I'd NEVER used Powerpoint, I'd barely used Excel, but I have used Word every day for eight years or so.
I flew through the PPT & Excel portions of the test, but the Word section killed me, not once, but twice! In the Word section, the test is set up where the testee must perform tasks only one way, the way the test programmer, intended, not the way someone who uses the program every day would.
I find it so annoying that it'll be the last test I take @ university to get my degree.
Re: tee-hee, he said testi
Re: tee-hee, he said testi