Ticket #643 (closed task: fixed)
Integrate displayModel branch in to NVDA
| Reported by: | mdcurran | Owned by: | mdcurran |
|---|---|---|---|
| Priority: | major | Milestone: | 2010.2 |
| Component: | Core | Version: | development |
| Keywords: | Cc: | ||
| Operating system: | Blocked by: | ||
| Blocking: | #58, #151, #200, #582, #605 |
Description
After the displayModel branch of NVDA is stable enough it should be merged in to main. As many other tickets rely on this happening, this ticket can act as a meta ticket so that we can keep track of all the other ones. Then we can reassess all ot them once this ticket has been closed.
Change History
comment:2 Changed 21 months ago by mdcurran
- Blocking 151 added
(In #151) All should be solved by using displayModel.
comment:3 Changed 21 months ago by mdcurran
- Blocking 200 added
(In #200) Implemented in changeset:displayModel,3464.1.10
Once displayModel branch is merged this can be closed.
comment:4 Changed 21 months ago by mdcurran
- Blocking 605 added
(In #605) Works great with displayModel branch. Once merged this ticket can be closed.
comment:5 Changed 21 months ago by jteh
I'm confused about the relationship between this ticket and #40...
comment:6 Changed 21 months ago by mdcurran
Slightly my mystake -- I didn't realize (or I forgot) that ticket 40 had quite a few comments related to the new display model -- I only thought it really contained my first new code intro comment.
I also didn't realize that all those display related tickets were already blocking 40. I'll learn to check next time :)
However, I think I'd prefer to keep it this way for now anyway as really the task is to merge displayModel, and all those tickets can automatically be closed once that happens, we're not really talking about major new features having to be implemented now.
But yeah, I could have saved myself the trouble if I'd looked :)
comment:8 Changed 21 months ago by jteh
- Status changed from new to closed
- Resolution set to fixed
Done in changeset:main,3508.
NVDA is developed by 