[openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 20 Jan 2004 13:55:09 +0100 CET
"Andrew Bachmann" <shatty@xxxxxxxxxxxxx> wrote:
> The other alternative is to use a separate mouse map struct based
> only on
> the buttons array, and then simply to interpret whatever you get
> passed
> in as that kind of struct. This suffers from the same kind of "evil"
> as the
> anonymous union earlier, with respect to interpreting the same bytes
> in
> a different way. Okay, so maybe the ugly more_buttons is the best
> option.
What about renaming those to other_buttons? Or just don't care at all
and see how many applications will break?? :-)
I mean I think it's okay to break source compatibility sometimes - as
long as binary compatibility is preserved. So we could export the old
get_mouse_map() calling _get_mouse_map() and are done with it.
Thoughts on that?
Bye,
Axel.
- References:
- [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- From: Andrew Bachmann
Other related posts:
- » [openbeos] broken struct mouse_map in InterfaceDefs.h
- » [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- » [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- » [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- » [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- » [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- [openbeos] Re: broken struct mouse_map in InterfaceDefs.h
- From: Andrew Bachmann