On 26/02/2010 7:43 AM, Pete Brunet wrote:
> #2 would provide a performance advantage for out of process because it
> eliminates additional cross process calls when the full set of targets
> is required.
IEnumVariant can do this as well. The first parameter to
IEnumVariant::next specifies the numbe
Peter,
Well you are getting older Ronnie. :-)
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Peter Korn
Richard,
Actually, if memory serves, I introduced this as a way to express
relationships in spreadsheets. Thus you could find out in a
spreadsheet showing quarterly gross expenses, costs, net revenue, and
results, that a given cell (say the lower right, total net for the
year) was derived fro
Rich, To me "has" feels more like a state rather than a relation so
IA2_RELATION_POPUP_INITIATOR_FOR seems to fit better.
I see that I also missed the reciprocal of IA2_RELATION_MEMBER_OF.
Should we add IA2_RELATION_GROUPING_OBJECT_FOR?
BTW, We should be careful to not add useless relations,
Nope. controller for indicates that an object controls another elsewhere in
the application. This was derived from the work we did with Sun on Java
where we had a problem in the SwingSet application. Here we had a series of
checkboxes that controlled the contents of a listbox (types of foods). We
Please let me know your preference.
1) Similar in style to other IA2 interfaces
HRESULT nRelationTargets ([in] BSTR relationType, [out, retval] long
*nTargets)
Returns the number of targets for the specified relation type.
HRESULT relationTarget ([in] BSTR relationType, [in] long index, [ou
I wonder if this is semantically captured by IA2_RELATION_CONTROLLER_FOR?
Not sure there is any harm to distinguishing POPUP_INITIATOR_FOR though
(or maybe POPPER_FOR).
cheers,
D
On 25/02/10 9:23 AM, Pete Brunet wrote:
> I can add IA2_RELATION_NODE_PARENT_OF.
>
> I just checked the list of relat
