https://bugs.documentfoundation.org/show_bug.cgi?id=153106
--- Comment #32 from ady <[email protected]> --- (In reply to Eyal Rozenberg from comment #31) > 1. We need to discuss what it's going to toggle, since we also have the > formula indicator and the clipped-extra-text indicator. Toggling comments is already available in menu and toolbar. You can have similar icons and menu entries for each kind of cell's "meta" info (comment indicator, formula indicator, comments, etc.), and one additional icon (and menu entry) to toggle all of these on/off. Have a sidebar too. The icons could be individual and/or have them all arranged together (similar to borders' icons, for instance). Some users might eventually ask for shortcuts. I would direct them to the Customize > keyboard dialog instead. > 2. This should resolve the grievance about the indicator interfering with > reading the text, but it does nothing to address the desire/need to make the > comment indicator more visible and eye-catching (which you may not share, > but many/most users do share). So, if that's implemented, we still want to > have the comment indicator be a triangle, which scales to some extent when > zooming in. "Eye catching, but for one moment only, then leave me alone and don't interfere with my view nor my work". A user would toggle in (rapid) succession the relevant icon or keyboard shortcut. Having even the current square on/off raises its contrast (because we respond visually much better to dynamic view vs static). If I have a "wrong" cell size, any artifact might clash with the content of the cell (even borders themselves could). Same goes for font type and font size, and alignment. I also presented additional alternatives for that other problem in the relevant topic. The area that the indicator covers doesn't need to be bigger in order to be more notable. In particular, I presented in that topic the possibility of "blinking". Think about a toggle for "blinking" the indicators. I wrote additional options in bug 154080 (such as timed blinking). You could also add some "bigger size when hovering over/closed to a cell", or different color, or shape (while hovering on/close to the cell _only_). IMHO, this is more distracting, not just letting the indicator be more discover-able. Other spreadsheet tools have additional info displayed, not _within_ the relevant cell but around it, and only when hovering. This behavior of displaying additional indicators is also a "toggle", on/off. But, beware not to increase the request for so many (graphic) resources that makes older systems unusable for LO. > > > (In reply to Eyal Rozenberg from comment #26) > > UX is no longer CC'ed. > (Please don't do that though, we're having a > discussion here.) OK. I wasn't planning on it anyway. > > > There is no real > > method for me to objectively compare, unless I can reproduce the effects > > with the current (LO 7.5) indicator vs the newly proposed one. > > Heiko, would you mind attaching the ODS file used in the screencast, to make > it easier for Ady to evaluate our proposal? The ods helps because anyone can replicate _all_ the attributes. Eyal previously mentioned that my screenshots were not a good enough representation of the original problem. That's because I am not using an inadequate combination of cell's height / width, font type, font size, alignment, and zoom factor. This is why I am convinced that the real (original) problem is on the user's side. There is a limit how much a UI can do without negatively affecting others; spoon-feeding cannot be endless. The way I previously generated the 4 screenshots was by using 7.6alpha vs 7.4.x. One has the patch, and the other still uses the current indicator. I simply used the same exact attributes in both versions. Now, even if I had the ods file from Heiko, I cannot compare it to the indicator seen in the screencast, because I don't have a version of Calc that generates them. After all, I am a simple final user, not a developer. > > > If I had a sample file that triggered the original request, > > It's a file with a cell with the number 13 in it. You can generate that and > play with the zoom effects to your heart's content... Not the same as having the ods (as I would had asked from the original reporter to attach). I could post an example of an incoherent cell size, font, alignment, even without comment indicator, and then we could all see that the real problem is on the user's side. As I explained, having the ods file would not be enough (for me) in this case, unfortunately. -- You are receiving this mail because: You are the assignee for the bug.
