| Summary: | Runaway column selection in Calc | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Phil Hibbs <snarks> |
| Component: | Spreadsheet | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | major | ||
| Priority: | high | CC: | bugzilla2, mike.hall |
| Version: | unspecified | ||
| Hardware: | x86 (IA32) | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Phil Hibbs
2010-10-26 16:16:29 UTC
Also it is not just column selection, any area select operation can cause this behaviour. how does one reproduce this? Do you need a document with some large amount of content etc. I only ask because I tried like you suggested ( admittedly with a blank calc doc ) and scolling either down or right to select rows or columns works fine for me. e.g. it selects cols/rows like a maniac but when I release the button the scrolling stops :-/ so.. am I missing some steps? ( or data? ) It may only occur when you have a complex chain of formulas. I was just about to upload an attachment that shows the issue, which I was experiencing on my quad-core Xeon laptop last night on LibreOffice, but trying it now on Go-oo 3.2.1 OOO320m19 (Build:9505) on my Pentium work machine it is responding just fine. I will try again this evening on LibreOffice. Yeah, I know about this. This problem tends to happen more often on Windows than on Linux, and it due to the redrawing requests getting queued up faster than the screen can redraw. I have a patch for go-oo that deliberately slows down the rate of scrolling as a temporary measure (for Windows only) which has not yet been ported AFAIK because I considered it to be a hack. Maybe we should port that patch to libreoffice. That should at least mitigate this problem until we put in the correct solution, which is to skip some of the redrawing requests in case of slow redraw. I'll take this meanwhile. I think the reason it happens on my home machine is it has a 1920x1200 screen so it is doing a lot more drawing tha my 1280x1024 work laptop. If I reduce the screen size to around 40x40 rows and columns, it doesn't happen, until I reduce the zoom so that more is on the screen again. It even happens with a blank spreadsheet if I zoom all the way out, so no need to attach a test case. Similar bug report was filed here as well https://bugzilla.novell.com/show_bug.cgi?id=514395 This is a Calc bug, therefore changed Component accordingly. This bug is substantially worse in LO 4.0.0 beta 1 making working in big spreadsheets extremely difficult. Therefore I am raising the priority to high-major. Me too has this problem. Reproducible with a blank Spreadsheet. I have 1920x1280 Screen-resolution. Omg, just noticed, that the last post was from 2012 :( Please don't tell, that this bug has such low severity rating? Btw, forgot Specs: Windows 8.1 Update 64 Bit, 8GB Ram, LibO 4.2.5 I can reproduce this problem too in the following way: Open a new spreadsheet. Move it to the second screen. Maximize the LibreOffice. Mark the first colum (A1:A1048576). Mark the next column at right outside of the screen ex. to column Z. There you can not stop until the col AMF (A1:AMF1048576) or something like that is selected. In this example i can reproduce this bug always Sometimes but not allways I can reproduce this problem with some rows ex. (A3:AMH15). Tested on Version: 4.2.6.3 Build-ID: 3fd416d4c6db7d3204c17ce57a1d70f6e531ee21 Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material > Your bug was confirmed at least 1 year ago and has not had any activity on
> it for over a year. Your bug is still set to NEW which means that it is open
> and confirmed. It would be nice to have the bug confirmed on a newer version
> than the version reported in the original report to know that the bug is
> still present -- sometimes a bug is inadvertently fixed over time and just
> never closed.
No activity for over a year????? The bug has been confirmed less then a month ago by Andreas Bernhaut on 4.2.6.3. I confirmed it in July and I did see that bug live at a customer of me yesterday, who is also on 4.2.6.3.
Bug still exists in 4.3.3.1 System: Windows 8.1 x64, German The two systems I mentioned before (confirming the bug in 4.2.6.3) has been Windows 8.1 x64, German, also. I have tried this in 4.3.2 both on a virtual machine and on my local machine (both Windows 7 64 bit) and cannot reproduce it - this machine is more powerful than the previous machine on which I experienced the problem and that may be relevant. I will try on my older machine next week. (In reply to Phil Hibbs from comment #16) > I have tried this in 4.3.2 both on a virtual machine and on my local machine > (both Windows 7 64 bit) and cannot reproduce it - this machine is more > powerful than the previous machine on which I experienced the problem and > that may be relevant. I will try on my older machine next week. More CPU power surely makes that bug appearing less often. But no need to reactivate your old machine, just zoom out to maybe 50%, maybe then it scrolls again?! Still have the 1920x1200 display? Even if the bug is not visible on "superfast" machines, or such with quiet small monitors, it should be fixed. Since there was already a fix (for a oo-fork) mentioned in the posts above, it should be very clear, where the problem is. We "just" need a nice developer to have a look at it (looking with big dog-eyes ;). |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.