Re: Accessibility for a custom text editor
Re: Accessibility for a custom text editor
- Subject: Re: Accessibility for a custom text editor
- From: Felipe Monteiro de Carvalho <email@hidden>
- Date: Fri, 20 Jan 2012 08:39:48 +0100
Ok, I figured out what was wrong ... I didn't notice before that there
is one event to return parameterized attibutes separated from the one
to return normal attributes...confusing.
Now I am stuck at the next point. The accessibility inspector keeps
saying that my value for AXNumberOfCharacters is null, but I set it
correctly like this:
else if (lLazControl is TCustomControl) and (lInputPasStr =
'AXNumberOfCharacters') then
begin
lOutputInt := UTF8Length(lLazControl.AccessibleValue);
lOutputNum := CFNumberCreate(nil, kCFNumberSInt64Type, @lOutputInt);
SetEventParameter(AEvent, kEventParamAccessibleAttributeValue,
typeCFNumberRef,
SizeOf(CFNumberRef), @lOutputNum);
CFRelease(lOutputNum);
Result := noErr;
end
Any ideas what is wrong here? I checked in the debugger that it
returns a valid handle for lOutputNum and that lOutputInt has value 5
like expected. I searched in google but I cannot find any examples of
people setting the value of AXNumberOfCharacters or
kAXNumberOfCharactersAttribute or
NSAccessibilityNumberOfCharactersAttribute.
Accessibility in Carbon seams to be some kind of black magic where no
one knows how it works?
--
Felipe Monteiro de Carvalho
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden