New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for applications running in an application player like java applications #4360
Comments
Comment 1 by jteh on 2014-08-03 22:23 |
Comment 2 by jteh on 2014-08-03 22:36 |
Comment 3 by jteh on 2014-09-11 04:15
|
Comment 4 by jteh on 2014-09-11 11:08
I'm particularly interested in whether this reports "eclipse" for users where Eclipse normally reports as "javaw". |
Comment 5 by driemer.riemer@... on 2014-09-11 16:45 appModule: <'eclipse' (appName u'eclipse', process ID 3112) at address 56773f0> |
Comment 6 by driemer.riemer@... on 2014-09-11 16:46 |
Comment 7 by jteh (in reply to comment 5) on 2014-09-11 23:20
Err, I'm a bit worried that it's using EditableTextDisplayModelTextInfo. I thought Eclipse was all IA2 now. What control was that? |
Comment 8 by driemer.riemer@... on 2014-09-12 05:43 |
Comment 9 by jteh on 2014-09-12 05:46 |
Comment 10 by driemer.riemer@... on 2014-09-13 05:47 |
Comment 11 by jteh (in reply to comment 10) on 2014-09-13 11:49
What does TextInfo report when you use this version of Eclipse with a release/master/next NVDA (not the try build)? |
Comment 12 by driemer.riemer@... on 2014-09-13 21:23 |
Comment 13 by manish (in reply to comment 4) on 2014-09-13 22:31 Replying to jteh:
|
Comment 15 by jteh (in reply to comment 13) on 2014-09-14 07:43
This still requires technical knowledge. Furthermore, if one user needs this, chances others will as well, so it makes sense to get such changes into the core. Filed #4454 for STS. |
Comment 16 by jteh (in reply to comment 12) on 2014-09-14 10:17
Okay. Can you please double check the TextInfo for the main edit area with both the try build and a master/next build? I'm very concerned that the try build is somehow causing EditableTextDisplayModelTextInfo to be used for Eclipse (as suggested by comment:5) instead of IA2TextTextInfo. The TextInfo shouldn't be affected by this change. If it is, something is very wrong. |
Comment 17 by driemer.riemer@... on 2014-09-14 10:59 " I still am confused as to why that other day it was different. |
Comment 18 by James Teh <jamie@... on 2014-10-10 08:14
Changes:
|
Comment 19 by jteh on 2014-10-10 09:41 |
Comment 21 by James Teh <jamie@... on 2014-10-21 04:28
|
Comment 23 by James Teh <jamie@... on 2014-11-06 04:46
Changes:
|
Comment 24 by jteh on 2014-11-06 04:47 |
Comment 25 by jteh on 2014-11-12 03:33 |
Comment 26 by nvdakor on 2015-01-03 03:43 |
Reported by heikofolkerts on 2014-08-02 19:18
Applications written in interpreted languages such as java applications use a kind of player when being run. So java aplications are all identified by javaw.exe or java.exe from NVDA. Since the applications ,may need very different and conflicting tweaks from an app module one cannot put the code for different applications in one app module.
Here is a proposal how this could be supported:
In case of java one would have to extract the package and class name of the main class that was given on the command line. In case of a python application one would need to identify the name of the main python file.
The support for example java applications is crucial for situations where a user would have to work with more than one java application and an specific application module willb be needed for one or more of them. In case of java applications this can happen quite often since keyboard support in those applications is usually very poor.
Blocked by #4556
Blocking #4454, #4569
The text was updated successfully, but these errors were encountered: