Best way to exchange data between a form and a unit

[cdbc]

Hi Hans
Yup, it's amazing how such a small cog in the /machine/ can have such a big impact, on making the /machine/ work correctly 
I think it's great that you're picking the MVP apart and getting to know the inner workings, by simplifying it to its basic components \o/\ö/\o/
The thing with CORBA interfaces, when you're creating directly to the interface (as we do), is you have to have some means of freeing the object again ...or (as you've found out) you'll have mem-leaks  I'd say, that such a method is mandatory in dealing with CORBA / RAW interfaces.
I'm glad to hear, you're 'chugging' along nicely 
Fair winds to you my friend and happy coding 
Regards Benny

[Hansvb]

'chugging' along. i like that.
Maybe the beginning of a light mvp version for quick small tools. I don't know yet. For me it is a study object that grows very, very slowly when I occasionally feel like doing something in Lazarus, but don't feel like continuing with something existing.

[cdbc]

Hi Hans
COOL  Gimme Gimme Gimme, Dang I'm curious \o/
Thanks Mate =^
Regards Benny

[Hansvb]

Don't expect too much from it. You can probably make this in 10 minutes. It's only a beginning but I'm slowly getting an idea of how it can grow.

[cdbc]

Hi Hans
I like it! Nicely done mate =^
True to the principle of "Separation of concerns".
If I may; One pitfall I can see, that you should be careful with is, when you use the result from 'SendToModelObj':

Code: Pascal  [Select][+][-]

1.   Edit2.Text:= FPresenter.SendToModelObj(@lRec, Edit2.Text, 'AnotherRec');

and the data comes through your /Observer-Callback/ and then gets assigned to the same view-object e.g.: 'Edit2.Text' -- One of the result assignments will _hide_ the other.  ...No danger, but you might miss some data and be hard pressed to find "Ze Bug".
Other than that, good work & understanding with keeping things working where they belong.
Regards Benny