C / C++ / MFC

rrrado wrote:

Because it is not necessary to use virtual tables just to make simple job Smile Just for one function

virtual int& GetID();

template <class T> class DRecord
{
    void DoReset() {  static_cast<T*>(this)->SetID(0); }  // accessing the ID
};

#define DEFINE_ID_FIELD(ID_NAME) \
   int NAME;
   void SetID(int value) { NAME = value; }
   int GetID(int value) const { return NAME; }

class A : public DRecord<A>
{
   DEFINE_ID_FIELD(A_XXX)
};

rrrado wrote:

I don't know OLE DB templates, thank you for tip. I'm using sqlite so I guess I cannot use them...

Snowprog77 wrote:

My question now is:
What benefits do I get from the second approach?

Snowprog77 wrote:

For me it looks like I just put one more step in the row. Is there less flickering?

Snowprog77 wrote:

What benefits do I get from the second approach? Is it faster? For me it looks like I just put one more step in the row. Is there less flickering?

• When the view is resized, work out if it's big enough to display all the controls. If it is, then disable the scroll bars. If it isn't, then you need to use SetScrollInfo[^] to tell the scrollbars how to display themselves.
• You need to add OnVScroll and/or OnHScroll handlers to deal with scroll messages. Use SetScrollPos[^] and ScrollWindow[^] to tell the view about the scrollbar parameters so it can work out which bit of the form should be displayed

template <class MapType, class DestinationType = MapType::referent_type>

typename MapType::value_type		source_type;

const int source_type* pFrom

const int std::string* pFrom