Hi Rich, At this point, since we couldn't find consensus and since this release was supposed to done last Fall and since I was informed that noone has implemented or shown a need for the three clipboard operations, I'm inclined to not hold up the release any further and handle this in a follow-on release if a project comes along that needs clipboard functionality and provides resource to drive the spec toward a well thought out definition of the clipboard methods.
Pete On 2/4/13 8:51 PM, Richard Schwerdtfeger wrote: > Hi Pete, > > The reason for the editing functions was to allow a voice reco > solution to select text, edit it, and perform clipboard operations for > the mobility impaired. It is additional work to have a voice reco > solution have to go through the additional work of doing the > additional keyboard simulations for doing that function. > > So, these are single actions. AccessibleEditableText also allows you > to replace text, and set attributes, which takes offsets and > replacement text/attributes. Accessible actions are single action > functions that don't take parameters. ReplaceText is not the same as > pasting from the clipboard. It is really nice to have all the features > in the same interface. Note: One could bind the single command > functions (cut, copy, paste) to the same actions in accessible actions. > > The other problem you have with actions is where do you apply it. Do > you know to apply it only to the document. If Editable text is applied > to text content within the document then you should now where to find > the interface. > > Rich > > > Rich Schwerdtfeger
_______________________________________________ Accessibility-ia2 mailing list Accessibility-ia2@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
