To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=102807
------- Additional comments from rbirc...@openoffice.org Tue Feb 9 14:31:25 +0000 2010 ------- @bfraga From users view you are right, that looks like a defect. I try to explane why this is a enhacement and not a defect. Apple's Multituch is new. No other Laptop has similar functionality. So we have to write new code, and implement it to the right place. If you know, that OOo has 8 Mio lines of code, you can expect, that is not a easy work. As defect we classify issues who describe a error in a allways existing fonctionality. The code for this feature does exist. Writing new code is allways more riskfull as only change same existing code. A enhacement and a feature request will be better tested as a defect. He hes a different internal workflow. So this change is for tecnical reason. Its important to make sure, that this issue will pass the right workflow. Same with te component. Normal users can't know that is a porting issue. But the right place is important. More then 200 developers works on OOo, they are very specialiced. If the issue is on the wrong place they will never see this issue. And Priority 2 are mainly Crashs and freeze so I change back. Thanks for understanding Greeting Raphael OOo Mac QA --------------------------------------------------------------------- Please do not reply to this automatically generated notification from Issue Tracker. Please log onto the website and enter your comments. http://qa.openoffice.org/issue_handling/project_issues.html#notification --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@porting.openoffice.org For additional commands, e-mail: issues-h...@porting.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
