Hi.
Getting this to the top since we need to get attributes API changes
together with relation changes.
In general Pete's proposal looks fine with me. Probably we might want
to return two arrays one is for name, another one is for values. But I
don't have strong opinion.
Does anyone have suggest
Technically we could create IAccessibleAttribute which is the pair of
name/value strings and return array of IAccessibleAttribute objects.
It should be a bit more nice than "name:value" strings. Btw, do we
need to have localizedAttributeName like we have for relations?
Alex.
On Sat, Oct 24, 200
Thanks for the input. How is this then?
Create IA2_2
- remove: attributes
- add:
- HRESULT attributeValue ([in] BSTR name, [out, retval] BSTR *value)
- HRESULT attributes ([out, size_is(,*nAttributes)] BSTR **attributes,
[out, retval] long *nAttributes)
where the return values are in the
Hi.
I think in general it's enough to have a method that returns attribute
value by its name. The method that returns an array of all attributes
is more helpful for debugging rather than in real life I assume
(please correct me if I'm wrong) to see what attributes are exposed at
all. But any way I
On 23/10/2009 2:04 AM, Pete Brunet wrote:
> We can add the following to IA2::attribute and IAText::attribute:
> HRESULT ([in] BSTR name, [out, retval] BSTR *value)
This looks good. Note, however, that this would require a new interface
due to the new method.
> Is an array of attributes also neede
Alex posted the following:
Additionally I would like to say about third problem which also concerns
to IA2 and ATK both. It should be nice to have a new method to deal with
object attributes and text attributes, i.e a method to get attribute
value by its name. It should help both client and server
