Phillip J. Eby wrote:
> Yes, it would, if you persistently stored the DataSkins in the other
> DataSkins. If you use an Attribute Provider, however, that loads them from
> a different Specialist+Rack, you'd be fine.
I get it now... (zpatterns zen is coming slowly but surely)
I have a basic imp
At 05:39 PM 11/6/00 -0800, John Eikenberry wrote:
>
>The base DataSkin will be in a Rack. Would there be any issues in making
>the embedded DataSkins (contained on the base DataSkins) use this Rack as
>well? Seems like it might result in the confusion about which DataSkin a
>PlugIn on the Rack wo
I have an idea for getting around my ConflictError problem without a major
redesign. But it involves DataSkins containing DataSkins. I have a few
questions about this...
The base DataSkin will be in a Rack. Would there be any issues in making
the embedded DataSkins (contained on the base DataSki
