Date: prev next · Thread: first prev next last
March 2016 Archives by date, by thread · List index


https://bugs.documentfoundation.org/show_bug.cgi?id=98539

--- Comment #4 from Yousuf (Jay) Philips <philipz85@hotmail.com> ---
Hi Cor,

Just to further clarify, this is my suggested design.

(In reply to Cor Nouws from comment #3)
1. Why do you choose to place Find All, Find Next, Replace and REplace All
in one line?
To me it looks there is a natural difference between Find and Replace, which
is supported by placing the groups in relation to the Find and Replace field.

The primary two buttons that users would constantly be using in the dialog are
the find Find Next and Replace buttons, so its important that they be next to
each other to reduce mouse movement and tab movement.

2. This is for Calc. What are the ideas for Writer, Impress?

They all use the same dialog UI file but hide or show different checkbox
options.

Further: do take into account the idea in issue 98417 please.

Yes i initially asked him to work on that and we decided to redesign the dialog
as well.

And if possible: issue 98544 is UI related and annoying too.

Well it shouldnt open the options if one option is enabled, it should remember
the state of whether the 'other options' was visible or hidden. I believe
someone started work on this functionality, but it seems to be broken (bug
98437).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.