Re: TActionList and datamodules

Andrea Raimondi wrote: 
Steve Troxell wrote:

Put the TActionList on a frame. Put the frame on the form and make it invisible. TActionList code is neatly separated out into the frame's class/unit. 


It looks like my english communication abilities are decreasing...
That's not the point I'm trying to make -_-

Regarding the workaround... I'm not sure it would work, but
anyway it's a fairly dirty trick, it can be good for a small
application, but a nightmare for more complex ones.

How is it any more of a burden than an actionlist on a data module? Seems to be roughly identical to me.

I use it in a quite complex application without much problem. The frame just happens to be visible rather than invisible, but identical to what I described in all other respects. The separation from the form code has been very helpful.


Plus, the goal of a frame is to show it, thus it would raise again the
separation issue :-)

The goal of a data module is to host data components. What's the difference? Yeah any nonvisual component *should* work on a data module and I have no problem with that. It's about as minor a deviation as whether Frame.Visible is true or false. Big deal. If I'm using a hidden frame as a component container, I find that an EXTREMELY minor detail.

Steve
.