On 11/24/00 10:06 AM, in article [EMAIL PROTECTED], "Adam Lock"
<[EMAIL PROTECTED]> wrote:
> Write to Microsoft/Logitech and ask them to change their driver code. The
> current drivers probably work by sniffing out the back/forward buttons based
> on windows classes, process names and other means. Mozilla/NS 6.0 are
> sufficiently different and don't even use native windows in the same way
> that this strategy will fail.
>
> A similar situation applies for the mouse wheel not working for certain
> drivers and on the Macintosh. Basically the driver is sending fake scroll
> events if it's over a window with horizontal/vertical scrollbars.
> Mozilla/NS6.0 windows don't have native scrollbars so the driver doesn't
> send anything to the window. Win32 drivers that send a WM_MOUSEWHEEL message
> work fine.
Wait a minute here. You admit that Netscape/Mozilla is using non-standard
window code on various platforms, and then blame the mouse drivers because
you created your own windowing environment for NS/Moz?
You know, I thought that when Jobs decided to abandon Apple's infamous NIH
policy, that maybe we had seen the light. Nope, NS/Moz has taken up the
banner. Every platform that has a gui has rules for windows, and in most
cases, classes/libraries/widgets/toolbox calls that allow you to implement
those windows and other interface elements without having to write your own
code. This way, you don't:
A) have to waste hours of time writing your own interface code
B) write interface code that breaks apps and drivers that expect the OS
-standard interfaces to be used.
But then again, you wouldn't be able to have wizzy-neat skins and themes.
After all, it must be hard ot get people to code the boring, dull,
functional parts of an app, because most of them are broke.
But my, don't the skins look cool.
Can someone at either NS, AOL, or Moz hire an adult as a project manager?
Please?
john
--
"95% of everyone you meet will be a moron. This is usually proven by looking
in the mirror each morning."
John C. Welch
