Use event pass instead of native invoke between components

0 views
Skip to first unread message

alsor.zhou

unread,
Aug 30, 2009, 9:28:18 AM8/30/09
to LibFetion
Currently (v1.0), most of the messaging mechanism was thru native
invoke, like
class FxSetting
{
FxMainWindow *m_mainwindow;
}
In this case, FxSetting will keep a mainwindow instance. It might cost
memories, and make code mysterious. If FxSetting really need that
mainwindow instance, it can be implemented thru signal/slot, which is
dynamically used and destroied.

Generally, different components should not contain other component
unless the sub component.

ThreeD

unread,
Aug 30, 2009, 10:02:24 AM8/30/09
to LibFetion
Hi alsor,
It just keep a point of mainwindow, so I think it will not cost
memory.
:-)

Thanks,
Dongdong

alsor zhou

unread,
Aug 30, 2009, 10:16:49 AM8/30/09
to libf...@googlegroups.com
Same like:) I'll check more carefully and show that:)

------
Design is making function beautiful.
Gtalk: alsor...@gmail.com
LinkedIn: http://www.linkedin.com/pub/vei-z/14/894/ab3


2009/8/30 ThreeD <libf...@gmail.com>
Reply all
Reply to author
Forward
0 new messages