Re: Setfocus / killfocus on cbutton
 
On 7 Dez., 03:30, Joseph M. Newcomer <newco...@flounder.com> wrote:
See below...
On Mon, 6 Dec 2010 14:39:32 -0800 (PST), mfc <mfcp...@googlemail.com> wro=
te:
On 6 Dez., 16:53, mfc <mfcp...@googlemail.com> wrote:
On 5 Dez., 20:29, Joseph M. Newcomer <newco...@flounder.com> wrote:
See below...
****
What I would do is invent a code, such as CITB_CHANGED, and use an O=
N_CONTROL handler to
handle this notification in the parent. The child button would do
GetParent()->SendMessage(WM_COMMAND, MAKEWPARAM(GetDlgCtrlId(), CITB=
_CHANGED),
(LPARAM)m_hWnd);
then I would have, in the parent's message map,
ON_CONTROL(CIBT_CHANGED, IDC_WHATEVER_BUTTON, OnWhateverChanged)
void CMyDialog::OnWhateverChanged()
{
updateaControls();
}
****
In the child button class you specifiy the id (GetDlgCtrlId = which
child button is affected by this change) but in the parent class
(dialog class) this information is not further used? Or did I miss
something?
Is there a better solution than this:
1) including all depending button controls to this call in the
OnInitDialog() (sometimes up to six other controls affected by the
spcific button)
m_Button1.SetParams(&m_StatCtrl, CImageTextButton::INCREASE, minval=
ue,
maxvalue, &m_Button2, &m_Button3);
How can I add these controls to one member-variable of the button
class? - using a clist (m_list.Add(m_Button2) and so on.... ?
****
Key here is how you encode it. I don't think there is a better way t=
han having the
SetParams method (or some variant) for each button, but I might cons=
ider, if I have a lot
of buttons, having something of the form:
static const struct {
CImageTextButton * ctl,
CStatic * target,
CImageTextButton::Direction dir,
int minvalue,
int maxvalue} Buttons[] = {
{&mIncreaseSomeValue, &m_SomeControl, CImageTextButton::INCREASE, 0,=
 1 },
{&m_OtherControl, CImageTextButton::DECREASE, 0, 1 },
{NULL, 0, 0, 0} // EOT
};
Could you tell me how you will declare / define this static struct in
the dialog class (so that this struct will be known in some other
methods in this dialog too)? I like the approach using a table / array
(Button[]) without knowing the size of the array at startup. So that
I can add as many buttons as I like.
****
Because it is a static struct, declared at the global scope level in this=
 compilation
unit, it is known to all methods in the compilation unit.  So nothing s=
pecial needs to be
done.   It is visible.  You could also define it as a static member o=
f your class, and the
syntax change is minor, and the effect is the same.  So you could say
class CMyDialog : public CDialog {
     protected:
        typedef struct {
        ...stuff
        } BUTTON_TABLE;
        static const BUTTON_TABLE Buttons[];
...
};
in the .cpp file:
static const CMyDialog::BUTTON_TABLE Buttons[] = { ... };
****
Is it better to install this struct within the dialog class or should
I use another headerfile which will be included in all dialog-classes
using this struct? And how can I use your initialization in these
classes?
****
In general, you will only need this in the one dialog class, which is wha=
t I was assuming
in the above example code.  Now, if you want to use this table in other=
 dialog classes to
build other button tables for other dialogs, you would put this typedef i=
n another header
file.  You would then include it in other dialog compilations. Note the=
 declaration
        static const BUTTON_TABLE Buttons;
would remain the same, but instead of putting the typedef right ahead of =
it, you would
move it to the separate header file.
****
    Buttons[] = {
   {&mIncreaseSomeValue, &m_SomeControl, CImageTextButton::INCREASE=
,
0, 1 },
   {&m_OtherControl, CImageTextButton::DECREASE, 0, 1 },
   {NULL, 0, 0, 0} // EOT
 };
****
Note that using the sentinel to mark the end is convenient, particularly =
if the function
doesn't have access to the definition.  If you want to use the length o=
f the struct, leave
the NULL terminator from the description and use _countof.
What I would do if I needed this in several places is create a separate c=
lass which has an
AddButtons method; then I could do something like
        Buttons.AddButtons();
or, if I needed the dialog reference,
        Buttons.AddButtons(this);
Note that you can refactor this code in as many ways as you want.  It's=
 Just Code.
****
The problem is that if I install the typedef struct as protected in
the same class, I`ve no access to this typedef in my static c++
declaration (cpp file) as well as if I try to add some class variables
to the struct in the cpp.
class CMyDialog : public CDialog
{
protected:
        typedef struct {
        ...stuff
        } BUTTON_TABLE;
        static const BUTTON_TABLE Buttons[];
   /* my specific controls in this dialog */
   CStaticField m_Field;
   CImageButton m_Btn;
};
in the .cpp file:
static const CMyDialog::BUTTON_TABLE Buttons[] = {{&m_Btn,
&m_Field, ....}};    //<- no access to class variables ;
It seems to me that there is no solution to solve this....
class CMyBtnStruct
{
 public:
     typedef struct {
        ...stuff
        } BUTTON_TABLE;
    void AddButtons(LPVOID ptr)
    {
     }
};
#include "BtnStruct.h"
class CMyDialog : public CDialog
{
protected:
        static const BUTTON_TABLE Buttons[];
   /* my specific controls in this dialog */
   CStaticField m_Field;
   CImageButton m_Btn;
};
//in cpp:
static const CMyBtnStruct::BUTTON_TABLE Buttons[] = {{&m_Btn,
&m_Field, ....}};    //<- no access to class variables ;
// same problems here according to the protected class members
void OnInitDialog()
{
    ///...
   AddButtons(this);
}
best regards
Hans
void CMyDialog::AddButtons()
{
for(int i = 0; Buttons[i].ctl != NULL; i++)
{
Buttons[i].ctl->SetParameters(Buttons[i].target,
Buttons[i].dir,
Buttons[i].minvalue,
Buttons[i].maxvalue);
}
}
and just call "AddButtons" in OnInitDialog. Note that it doesn't cha=
nge the fact that you
have to specify all the buttons, but it handles it in a different wa=
y.
I`ve now two small structs to get all required values for updating all
buttons
struct Btn
{
CImageTextButton *ctlLeft; /* << */
CImageTextButton *ctlRight; /* >> */
CImageStatic *target; /* cstatic field */
CImageTextButton::Direction dir;
int minvalue;
int maxvalue;
};
struct BtnCtrl
{
Btn ctrl;
Btn subctrl;
CDWordArray dis_subctrl; //situations where the
subctrl is complete disabled
};
The struct BtnCtrl will include an additional subcontrol as well as a
wordarray which defines the situations where the subcontrol will be
disabled according to the value of the ctrl-staticfield. I`ve some
cstatic fields which can disable/enable another cstatic field and
their two buttons (<< and >>).
best regards
Hans- Zitierten Text ausblenden -
- Zitierten Text anzeigen -
Joseph M. Newcomer [MVP]
email: newco...@flounder.com
Web:http://www.flounder.com
MVP Tips:http://www.flounder.com/mvp_tips.htm- Zitierten Text ausblenden =
-
- Zitierten Text anzeigen -- Zitierten Text ausblenden -
- Zitierten Text anzeigen -