the only way to avoid this is to simply not set the control's position within the ON_UPDATE_COMMAND_UI handler. The ON_UPDATE_COMMAND_UI handler is used to implement the visible state of a GUI element's, it's not intended to be used to update data which might be associated with that control. And IMO this is really senseful, since if one uses a ON_COMMAND_UPDATE_UI handler to change any data may initiate another ON_UPDATE_COMMAND_UI.

So, I would suggest you add a 'int' member to your applications document - in 'OnMapDDIDetails' you can retrieve its value as you now do for 'iDDIViewDetails'. In 'OnUpdateMapDDIDetails' just handle visibility/disabled-state of the control. Add a 'OnActivateView' handler and use the 'SetPos' there as you before did in 'OnUpdateMapDDIDetails'.

Featured Post

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Errors will happen. It is a fact of life for the programmer. How and when errors are detected have a great impact on quality and cost of a product. It is better to detect errors at compile time, when possible and practical. Errors that make their wa…

Many modern programming languages support the concept of a property -- a class member that combines characteristics of both a data member and a method. These are sometimes called "smart fields" because you can add logic that is applied automaticall…

The viewer will learn how to pass data into a function in C++. This is one step further in using functions. Instead of only printing text onto the console, the function will be able to perform calculations with argumentents given by the user.