then SmartWin++ has no direct replacement. Of course you can query the widgets in the dialog yourself.
There is also a class InDialog, as demonstrated in the sample iolib or the sample WidgetGraph, that can pass in variables, operate as a modal dialog, and then return the values back to the parent class.
One nice feature is that dialog is generated from the list of variables passed to the class at runtime. That is right, it generates the appropriate Widgets for the int, float, bool, string, COLORREF, directory, ChoiceString, etc, passed into InDialog.
One drawback is that Cancel does not revert all the values back to their original state.
It looks like this:
#include "io/InDialog.h"
COLORREF itsAxisColor, itsPointColor;
bool axisPresent;
int itsPenWidth;
int itsHistoSections;
Thank you for the answer. But what I'm asking for is slightly different, because I need data binding in dialog that was designed in Visual Studio dialog designer, not in run-time. MS DDX implementation uses ugly, non-c++ approach. I think something like data binding should be implemented by using aspects or smth like that. Am I wrong?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm, well if the controls were specified for the resource compiler, then you can turn them into SmartWin++ Widgets with the subclass functions. And then you have the ability to set and get the values with Widget member functions.
Cannot locate how to do data binding in dialogs. Can someone show me the way?
Nice library anyway.
If you mean similar to MFC's DDX, as described here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vccore/html/_core_dialog_data_exchange.asp
then SmartWin++ has no direct replacement. Of course you can query the widgets in the dialog yourself.
There is also a class InDialog, as demonstrated in the sample iolib or the sample WidgetGraph, that can pass in variables, operate as a modal dialog, and then return the values back to the parent class.
One nice feature is that dialog is generated from the list of variables passed to the class at runtime. That is right, it generates the appropriate Widgets for the int, float, bool, string, COLORREF, directory, ChoiceString, etc, passed into InDialog.
One drawback is that Cancel does not revert all the values back to their original state.
It looks like this:
#include "io/InDialog.h"
COLORREF itsAxisColor, itsPointColor;
bool axisPresent;
int itsPenWidth;
int itsHistoSections;
void chooseProperties( const SmartWin::MouseEventResult & mouse )
{
SmartUtil::tstring title= _T("Graph parameters");
InDialog myInDialog( this, title );
myInDialog
.add( _T( "Axis present?" ), & axisPresent )
.add( _T( "Point color ..." ), & itsPointColor )
.add( _T( "Axis color ..." ), & itsAxisColor )
.add( _T( "Graph width" ), & itsPenWidth );
if ( 0 == itsY.size() )
{
myInDialog.add( _T( "Histogram sections" ), & itsHistoSections );
}
if ( IDCANCEL == myInDialog.createDialog() ) return;
// The new values have appeared in the variables now.
this->updateWidget();
}
best regards, Andrew
Thank you for the answer. But what I'm asking for is slightly different, because I need data binding in dialog that was designed in Visual Studio dialog designer, not in run-time. MS DDX implementation uses ugly, non-c++ approach. I think something like data binding should be implemented by using aspects or smth like that. Am I wrong?
Hmm, well if the controls were specified for the resource compiler, then you can turn them into SmartWin++ Widgets with the subclass functions. And then you have the ability to set and get the values with Widget member functions.
WidgetTextBox * itsHexTxt
itsHexTxt = this->subclassTextBox( IDC_HEXEDIT );
itsHexTxt->setTextLimit(32);
itsHexTxt->setFocus();
itsHexTxt->setText( label );
itsParent->dataFromDialog( itsHexTxt->getText() );
This might be sufficent. If not, how should the widget map to a variable with string, int or double type ?
Can we easily insert "aspect" into dialog behaviour to change specified variable if control value has been changed by user?