[ELwardi]

Hi all,


I'm developing an independent library of classes to do various tasks, and often I find myself in need of a reference to a field the solver operates on/with.


As far as I can tell there are two options:
- Pass the reference to the class through its constructor.
- If the field is registered, get it from the object registry.



I do prefer the second option, but I'm facing a weird problem:


Assume I have a pure virtual class MyModel with a static ::New method that selects and constructs a "model" class. MyModel creates some volScalarFields and instantiates a handful of MyObject (also virtual) children.




MyModel, MyObject and their child classes constructors take a reference to the mesh as an argument, which is then used to initialize a member variable. It's like a habit of mine :

const fvMesh& mesh_;

The following code, in a member function of a child of MyObject, should get a (local) reference to K field:

const volScalarField& k = mesh_.db().lookupObject<volScalarField>("K");

but it doesn't. When the case is run, only volScalarFields generated by MyModel class are available!!!


The weird part is that MyModel takes only a "reference" to the mesh but it can't find some fields that are registered with that mesh object???

Do MyModel and/or MyObject need to inherit from some other class?



This being a bug in foam-extend 4 has low probability but I can't get my head around it! Any help/thoughts is appreciated.

[ELwardi]

It seems I was looking at the wrong place again:


Before starting the library, I decided to register everything to mesh (fvMesh inherits from objectRegistry) but after a while I got confused and started to register things to mesh.db() member.


So,

mesh.db().lookupObject<volScalarField>("K")

wouldn't work but

mesh.objectRegistry::lookupObject<volScalarField>("K")

would .