[Nvda-dev] renaming of navigator object

[Roberto Pérez de Paz]

Dear Mgr:

I don't know one specific screen reader which uses the system that I 
proposed in my message. I'm only finding one way for organizing and 
providing the information available in MSAA to the user because the 
system we are currently using is difficult to understand for many 
people. Even I didn't think in a real and visible object list which 
overlaps the content of the display but simply in a more logical 
mechanism to present the content of the Window to the blind user. I know 
this is a big problem. I'm not a python programmer but I know the 
differences between python and Visual Basic 6.0 languages.

I think the programmers are doing a great work with this free screen 
reader and it's too necessary. I appreciate it too much.

Thank you for your explanation.



El 28/12/2009 13:18, Mgr. Janusz Chmiel escribió:
> Dear users,
>
>    I think, that The approach, which is now being used in NVDA is 
> ammazing. The programmers techniques, which are necessary for 
> constructing lists with objects are not easy while programming in 
> Python. And, what is very, very important, if MR Curan and James Tech 
> would start to develope this new function for activating and wieving 
> objects, The editfield with information about those objects will 
> overlap The content of The screen. Next issue, if AN application is 
> having many various objects, taking those information from MSAA can 
> take in some cases more than 30 seconds even while using modern 
> computers.
>
>    Next issue is, that if Python would be used for this tasks, The 
> process would be slov, so next complex librari written in C 
> programming language would have to be used.
>
> I like The approach of navigation objects while using NVDA. Even 
> commercial and expensive screen readers, which are using display 
> chaining manager and other API calls for getting necessary information 
> from The screen are having also some shadow aspects.
>
> 1. Random crashes of those programs can occur more often then while 
> working with NVDA, which is in most cases based on Microsoft API 
> functions call and on MSAA. If somebody would want to make The new 
> object navigation mechanishm, everybody can do this, Python and 
> Microsoft Visual C++ or Microsoft SDK are awailable free of charge, 
> only programmers knowledge are required.
>
> I AM using one screen reader, which is using The approach to The 
> object navigation, which MR Roberto Pérez de Paz explained.
>
> Everythink is working ammazingly, eccept those two very important 
> shadow effects.
>
>    Some objects are shown but user do not know, if those objects are 
> visible or not, in some cases, user can wiev and would try to click on 
> some object, which can be used only, if some other button will be 
> activated.
>
> 2. If more than 3 or 4 Windows are opened, it is sometimes inpossible 
> to click on The object and text from editable fields are interfering 
> with other texts, if visually impaired user will not minimize or hide 
> other Windows by using Wonderfulicon application, or 4Ttrayminimizer 
> free.
>
>    Every programmers approach is having some positive and some shadow 
> aspects. If i should choose, i would rather stay in The NVDA navigator 
> object techniques, which are used for now in NVDA. User can know, if 
> object is invisible or not, and those information can be acquired 
> without using display chaining manager. Thank's to The functions, 
> which can copy The text from current object to The clipboard, i can 
> copy some long messages to The clipboard and use it in other 
> applications.
>
> But it is only all my personal opinion. Please, remember, that Python 
> programming language is not Microsoft Visual Basic 6.0, where 
> programmer can click on some custom controls and then programmers are 
> able to only simply write some commands to The right places, other 
> commands are predefined automatically. For example, while using form 
> mode.
>
>
>
> _______________________________________________
> Nvda-dev mailing list
> Nvda-dev at lists.nvaccess.org
> http://lists.nvaccess.org/listinfo/nvda-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nvaccess.org/pipermail/nvda-dev/attachments/20091229/1e96e843/attachment.html>