Comment 4 for bug 234808
Revision history for this message
| lee cowell (lewac) wrote Re: [Bug 234808] Re: well we couldn't find a workaround... | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Chris... well the bug still exists as initially reported on our systems. and it still exists in 2.4.1. now I've really no clue why hardware should affect what the app observes from the keyboard. however the problem exists on an ASUS P5N-SLI and a ASUS P5L-MX motherboard. It also exists on every other system here thus I seriously doubt as mentioned that this is a hardware issue in any form. not only that it also fails in the windoze version (also 2.4.1)!
perhaps I'm misunderstanding what "highlighting" IS? what I expect regarding highlighting is like taking a "highlight pen" and drawing across some text to "highlight" it in some lighter color (typically light "neon" yellow or pink) to make the text "stand out" (the BACKGROUND color of each character entered is thus modified). word for example has no issues with doing exactly what I've described here... and its what I expect "highlighting" to actually do. note that mouseover defines the word "Highlighting" within the toolbar icon hint field as well.
of course you may chose to close the "book" on it but non-the-less the problem DOES exist and its DEFINITELY within the coding. perhaps I'll take a look at it myself IF it continues in the version 3.x release (I'm assuming its written in one of my LEAST favorite languages (C++). well hopefully the code is well commented! as mentioned once the user turns the thing on from there persistence is the word of the day.
sincerely, -Lee
----- Original Message ----
From: Chris Cheney <email address hidden>
To: <email address hidden>
Sent: Tuesday, July 22, 2008 10:12:31 AM
Subject: [Bug 234808] Re: well we couldn't find a workaround...
We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on the current status, under the Status column, and change
the Status back to "New". Thanks again!
** Changed in: openoffice.org (Ubuntu)
Status: Incomplete => Invalid
--
well we couldn't find a workaround...
https:/
You received this bug notification because you are a direct subscriber
of the bug.