On Feb 14, 2006, at 6:57 AM, Chuck Pelto wrote:
On Feb 13, 2006, at 7:36 PM, Charles Yeomans wrote:
Looking at it from the other perspective, the old ContextualMenu
object, how does one access the 'tag' feature?
One does not. I recommend solving the problems with the
ConstructContextualMenu method.
Then it looks like there is a bug in the new approach to contextual
menus.
Here's what I've done:
[1] Created a MenuItem class object at the project level as cmInfoP.
[2] Moved the code from Open in the old ContextualMenu object of the
window to the ConstructContextualMenu activity of the listbox.
[3] Called upon the method I've established in a module to handly
routine activities, e.g., BuildComplexCM. This method takes the CM, a
default list of text to be loaded at the first level and a VCursor of
data from a table to be used to populate the rest of the CM and builds
the CM.
Here's the call to the BuildComplexCM() method....
Routineer.BuildComplexCM(cmInfoP, defaultList, addsCursor)
Here's the params of the BuildComplexCM()....
theCM as MenuItem, defaultList as string, addsCursor as VCursor
At compile I get...
Parameters not compatible with this function.
So, what's wrong here?
The compiler has told you what it thinks is wrong. What is the object
cmInfoP that you're passing to BuildComplexCM? It should be an object
of class cmInfoP that was created with a line of code like
cmInfoP = new cmInfoP.
And the class cmInfoP should be a subclass of MenuItem.
But unless you're adding some functionality to this class, you probably
don't need it. Instead you would just create a new MenuItem object and
pass it to BuildComplexCM.
--------------
Charles Yeomans
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
