From: Big T. <big...@gm...> - 2009-10-09 17:45:08
|
Still, a typical scenario is, CMyKnob::onMouseDown(where, buttons) calls CAnimKnob::mouse(where, buttons), and has no idea if "where" is going to be modified by this call or not, and can only know by checking CAnimKnob implementation. I would be in favor of enforcing it, by making it const in the method signature. 'Tick > > On Oct 6, 2009, at 10:30 PM, Big Tick wrote: > >> Well, in this case, you may want to consider making the "CPoint >> where" >> parameter (in all mouse methods) a const as well. If a class deep >> down >> in the inheritance tree modifies this parameter, this will generate >> tricky bugs - so it's better to let the compiler forbid it. > > No, the view container will take care of this. The view can alter the > where point without consequences to the other views. > > cheers > arne > > > ------------------------------------------------------------------------------ > Come build with us! The BlackBerry(R) Developer Conference in SF, CA > is the only developer event you need to attend this year. Jumpstart > your > developing skills, take BlackBerry mobile applications to market and > stay > ahead of the curve. Join us from November 9 - 12, 2009. Register now! > http://p.sf.net/sfu/devconference > _______________________________________________ > Vstgui-devel mailing list > Vst...@li... > https://lists.sourceforge.net/lists/listinfo/vstgui-devel |