SOLVED / Re: How to make an own panel work like an e.g. TextField / joining the model hierarchy of page/form

Hi Martin, thanx, its working, now. I had some additional convenience constructors in my panel with empty model object inits, because some days ago I always ran into "try to set on empty model object exceptions". I kept them and I think they forced side-effects. Just having one, only with an i

Re: How to make an own panel work like an e.g. TextField / joining the model hierarchy of page/form

Hi Patrick, On Wed, Jul 24, 2013 at 10:36 AM, Patrick Davids wrote: > Hi Martin, > concerning the IComponentInheritedModel I did not not try anything in my > panel since yet, because I suppose it should work from the scratch, when > a manually wrap the ModelObject on form level into CompundPrope

Re: How to make an own panel work like an e.g. TextField / joining the model hierarchy of page/form

Hi Martin, concerning the IComponentInheritedModel I did not not try anything in my panel since yet, because I suppose it should work from the scratch, when a manually wrap the ModelObject on form level into CompundPropertyModel. As I can see CompoundPropertyModel is an IComponentInheritedModel,

Re: How to make an own panel work like an e.g. TextField / joining the model hierarchy of page/form

Hi, On Tue, Jul 23, 2013 at 4:17 PM, Patrick Davids wrote: > Hi all, > I implemented a "TextField-Panel". > Its kind of FormComponentPanel, but not really... do not have a > convertInput() situation. > Just additional behaviors and some own l18n stuff... > > Its already working fine, but what I

How to make an own panel work like an e.g. TextField / joining the model hierarchy of page/form

Hi all, I implemented a "TextField-Panel". Its kind of FormComponentPanel, but not really... do not have a convertInput() situation. Just additional behaviors and some own l18n stuff... Its already working fine, but what I always have to to is, getting the modelobject manually and forward into m