alam:
The way I did it was to build an observer, wait until conditions were met, then I would run this code:
do
{
InterfacePtr <IPanelControlData> PControlData(this, UseDefaultIID());
ASSERT(PControlData);
if(PControlData == nil)
break;
IControlView* CView = PControlData -> FindWidget(kWPCPSelPgEdtBxWidgetID); // get control view for widget
ASSERT(CView);
if(CView == nil)
break;
if(widget == kWPCPPSelPg__RWWidgetID) // some kind of test to determine what you want to do...this step may not be necessary.
{
CView -> Enable();
WPCPDialogObserver::bTextEnabled = kTrue; // This was a flag I needed to set for other parts of the code.
}
else
{
CView -> Disable();
WPCPDialogObserver::bTextEnabled = kFalse;
}
}
while(kFalse);
If the tool is in another dialog, then create a static pointer to itself in the class, create a static member function to retrieve that pointer, be sure to set the pointer to this when initializing the plugin, and when leaving the plugin set it to NULL. Then call the member function to get the pointer, and use the pointer to call the function that will enable/disable the tool you want enabled/disabled. It would look something like this:
MyDialog MyDialog::ptr = NULL;
class MyDialog::CDialogController (Or observer, whatever is more appropriate)
{
...
static MyDialog *ptr;
static GetMyDialogPtr() {return ptr;}
}
MyDialog::MyDialog()
{
ptr = this;
}
MyDialog::~MyDialog()
{
ptr = NULL;
}
MyDialog::enableTool()
{
// Whatever
}
/* and in other code */
OtherClass::DoSomething()
{
MyDialog *DialogPtr = MyDialog::GetMyDialogPtr();
if(!DialogPtr)
{
CAlert::ErrorAlert("Sorry, that plugin is not active");
/* Take appropriate remedial activity */
}
DialogPtr -> enableTool();
}
There may be some problems with threading issues with this scheme; I haven't had to cope with that yet, but I suspect there are some moderately simple steps that could be taken to make this thread safe.
I hope this gives you an idea of how you might do what you want to do.
R,
John
9
Replies
AdChoices