<html><head></head><body><div dir="auto">Hi Paul<br><br>It would be much appreciated if you could report the issue on our bug tracker, so we can hope to figure the issue out and eventually fix it: <a href="https://bugs.documentfoundation.org/">https://bugs.documentfoundation.org/</a><br>These here lists are not for reporting bugs.<br><br>Please include a sample document, and details about your LO version (copied from Help > About LibreOffice) and the View options you use (e.g., do you use dark mode?).<br><br>Thank you.</div><br><br><div class="gmail_quote"><div dir="auto">On 2 August 2024 12:53:20 am AEST, paul hofseth <paul@hofseth.co> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">sirs,<br><br>I occasionally look at your dialogues and at times misguidedly complain about program stability rather than lack of "bells and whistles" .<br><br>I do realize that your task is dealing with the user interface and not with the data mechanics, but do hope that you have communication lines that concern program usefulness-.<br><br>This time I am sorely tempted to comment on the disability of reading monopolistic texts in docX format even if it lies outside your remit.<br><br>When working with our new book i have discovered a msjor annoyance when my co-authors use microsoft or apple. Black text on black background is not enlightening in any sense of the word.<br><br>p.<br><br>Den 01-08-2024 16:33, skrev Csongor Halmai:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">Hi Heiko,<br><br>you wrote this:<br><br> + necessary if the app DPI differs from the screen DPI (Csongor)<br><br>but I didn't say this.<br><br>I meant in my comment that this feature would be useful when you want to see more information than the resolution of your screen (and your eyes) allows. You could magnify the region of interest (ROI) while you still can see the big picture as well.<br><br>I created a mimicking screenshot in GIMP how I think it should look: <a href="https://i.ibb.co/WW0WsxC/magnifier-sample.png">https://i.ibb.co/WW0WsxC/magnifier-sample.png</a><br><br>Disclaimer: for the screenshot, I used the Spherize filter of GIMP, which is geometrically not identical to a magnifier lens but shows well enough what I would like to see.<br><br>In order to not hide anything from the underlying screen, it is essential that the center of the circle shows things larger than their original size but at the same time, around the edge, things look smaller. This way, the magnifier doesn't cover anything, just shows some distortion around the edges.<br><br>A realistic lens effect can be seen here: <a href="https://youtu.be/XtCW-axRJV8?t=271">https://youtu.be/XtCW-axRJV8?t=271</a><br><br>I think this would be such a useful feature that it should be supported at operating system level.<br><br>Csongor<br><br><br><br><br>On 1/08/2024 04:56, Heiko Tietze wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><div dir="auto">Present: Sahil, Eyal, Heiko<br>Comments: Mike, Justin, Stephane, Stuart, Cor<br><br>Tickets/Topics<br><br>(Suggested bump-up (Eyal):<br> * Cell selecting fat border looks ugly especially if you selected some<br> cell range, it also can block content in other cells<br><a href="https://bugs.documentfoundation.org/show_bug.cgi?id=161709">https://bugs.documentfoundation.org/show_bug.cgi?id=161709</a><br> + Rafael: Made commits to improve the cosmetic situation, consider<br> the bug fixed.<br> + Rafael: This was done to resolve 143733, which requested the<br> rectangle not cover the active cell<br> + Heiko: Suggest accepting the current situation for now<br> + Eyal: Serious degradation of UX - text in surrounding cells<br> partially hidden, can make one value appear as another due<br> to hiding.<br> + Eyal: Suggest back-out of changes to before 143733, for now, and<br> reconsideration. Must fix this for 24.8 release.<br> + Eyal, Mihai, Rafael, Roman, flm2: Excel active cell rectangle looks<br> nice<br>=> please discuss at Bugzilla or the mailinglists (Heiko)<br>)<br><br> * No option to automatically indent multiline list entries to align<br> with numbering followed by space<br> + <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=156071">https://bugs.documentfoundation.org/show_bug.cgi?id=156071</a><br> + line up *subsequent lines* of each list entry, see c12<br> + no good example for the necessity (Mike, Cor, Heiko)<br> + mandatory to have this as cross-platform feature (Justin, Cor)<br> + A tab is, in the general sense, an inherently flawed solution,<br> because once your number exceeds the tab width - you'll overflow<br> and the alignment will be messed up (Eyal)<br> + Request is reasonable (Eyal):<br> + Follows a different aesthetic principle: Fixed amount of space<br> between number and paragraph content v-start rather than uniform<br> content v-start across all paragraphs<br> + Should be implemented via a paragraph feature to move all lines<br> further in to respect the maximum constraints on each individual<br> line (e.g. numbering, wrapping around frames etc.), ensuring<br> that the paragraph's v-start is uniform across all lines, without<br> having to set it explicitly using indentation and/or tabs.<br> + Should be usable even without numbering being active (an aspect<br> of a paragraph's style)<br> + requires probably also to start a list from any number (Heiko)<br> + MSO does exactly the same as we do (Heiko)<br> => comment<br><br> * Tab stop of list contents increases then decreases in default<br> Roman numeral list, looking messy<br> + <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=162133">https://bugs.documentfoundation.org/show_bug.cgi?id=162133</a><br> + Microsoft Office forces right alignment for Roman numerals, often<br> with horrible results (Justin)<br> + right-alignment is not the right solution => WF (Stephane, Cor)<br> => solution follows bug 156071<br><br> * PIVOTTABLE: Formating Pivot Tables<br> + <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=51732">https://bugs.documentfoundation.org/show_bug.cgi?id=51732</a><br> + double-click brings up the Data Field dialog currently, add<br> a context menu (Stephane. Cor)<br> + perhaps more obvious via push button? (Sahil)<br> => provide a context menu for the functions<br><br> * Magnifier Tool for a quick overview and spot zoom into a document<br> in Multiple-page view<br> + <a href="https://bugs.documentfoundation.org/show_bug.cgi?id=162101">https://bugs.documentfoundation.org/show_bug.cgi?id=162101</a><br> + magnifier is always just a click away, eg. Win + +/- on KDE<br> + bug it does not render again with a higher resolution (Heiko)<br> + "magnifier" would be an excellent feature *in general* (Stuart, Cor)<br> + necessary if the app DPI differs from the screen DPI (Csongor)<br> + duplicates / relates to bug 101646 "UI option "Scaling" was removed"<br> with a lot duplicates itself<br> + weird relation to multi-page view; suggest to do with low<br> priority (Eyal)<br> => comment<br><br></div></blockquote></blockquote></pre></blockquote></div></body></html>