TActionList and datamodules

Hello.

I've been facing today a fairly weird problem.
It's about TActionList class and datamodules.

Did you know that TActionToolbar doesn't work with
TActionLists originating from a TDataModule?
Well, this was an interesting discovery.

My problem with the approach of having TActionList
instances on a form is that it breaks separation
between business rules and presentation.

While this might look like an OOP design problem
(which would pertain to the .oodesign group) what I'm
talking about here is at a slightly higher level.

That is, the TActionList should be taken as a mere
example to discuss about datamodules and their use
with non-visual components.

My personal opinion is that a TActionList can be
compared functionally to a TDataset descendant.
Obviously, they serve entirely different goals, but
both represent something "abstract that relates(or
could be related to) the presentation layer of a
software.

Thus both *should* be on the datamodule.

This should also be true for things like TOpenDialog and
such components, but not - for example - for TMainMenus or
TPopUpMenus because in those cases the visual functionality is
*preminent*.

What do you think?

TIA,

Andrew
.