Issue 79311 - BASIC IDE/Usability: Dialog controls invisible/cannot be distinguished
Summary: BASIC IDE/Usability: Dialog controls invisible/cannot be distinguished
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-07-06 07:42 UTC by joerg.skottke
Modified: 2017-05-20 10:55 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

Mockup to show the problem and two suggested solutions (22.22 KB, image/png)
2007-07-06 07:45 UTC, joerg.skottke
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description joerg.skottke 2007-07-06 07:42:30 UTC
When drawing a control in the dialog editor, some controls can be easily
identified, such as the frame control or the pushbutton. However, many controls
just appear as white boxes on the dialog editor, others do not even have a
different background color or a frame. Take the new tree control as sample. If
you have several of these controls there is no way of distinguishing them unless
you open the property browser for the control.

Attaching screenshot to illustrate the issue, the small pictures are numbered,
description follows here:
1) Two controls on a dialog in design mode - one is invisible, one is - you
might want to guess
2) Selected both, there really are two controls, no joke!
3) Suggested solution 1: Take the tiny picture from the formcontrols palette and
place it in the center of the control (unscaled), give the area a background
color and a border
4) Suggested Solution 2: Draw a bitmap into the area of the control that
indicates its type (scaled) with a border
Comment 1 joerg.skottke 2007-07-06 07:45:00 UTC
Created attachment 46561 [details]
Mockup to show the problem and two suggested solutions
Comment 2 frank.loehmann 2007-07-06 08:44:45 UTC
That's exactly what I have asked in my latest e-mail to the iteam. It is not
acceptable to have a white or invisible frame in the design mode even for 2.3.
At least we need to have a surrounding border and an icon inside like proposed
by Joerg. If not we have to disintegrate the workspace for 2.3.
Comment 3 joerg.skottke 2007-07-06 09:34:53 UTC
@fl: Your mail was the reason why i wrote this issue. Actually i consider this a
bug, not an enhancement. It is almost impossible to work with the dialog editor
if you cannot distinguish the controls, that's a major flaw in usability which -
to my knowledge - even qualifies for a P2 priority.
If you agree on that, we could change the status to DEFECT and increase the
priority, this is not exactly UI relevant (no translations involved) so it might
actually have a good chance of getting in if fixed soon.
Comment 4 ab 2007-07-06 11:37:50 UTC
Accepted as 2.4 enhancement, details needs to be discussed.
Completely control invisibility is probably caused by the i79128
repaint problem. STARTED
Comment 5 joerg.skottke 2007-08-14 13:05:28 UTC
*** Issue 80543 has been marked as a duplicate of this issue. ***
Comment 6 joerg.skottke 2007-08-14 13:11:53 UTC
Setting broken flag, changing to DEFECT. issue 80543 reports that this was ok in
OOo 2.2.1
Comment 7 joerg.skottke 2007-08-14 13:29:50 UTC
IN agreement with MD i make this task a showstopper. Depending on available
resources we should try to get this one fixed.
Comment 8 ab 2007-08-15 08:43:05 UTC
ab->jsk: It absolutely makes no sense to regard this issue as 
showstopper as it mainly describes ways to enhance the identifi-
cation of controls in the Dialog Editor design mode. 

The showstopper problem of completely missing frames or wrong
background color is mentioned only secondary. But this should be
the only subject of a showstopper task. We shouldn't mix clear
paint/VCL related defects with nice-to-have user experience 
related enhancements.

Besides this I couldn't reproduce the missing frame / background
color problem on any Windows version. Obviously this is platform
dependand and not OS==all.

Suggested solution: Check which platforms are affected at all
and either un-duplicate i80543 - that for sure is no duplicate
of this issue - and change the OS accordingly. Or submit a new
issue concerning the no-frame/background problem and make i80543
a duplicate of the new one.

In any case - see AW's comment in i80543 - this is no Dialog
Editor, not even a Drawing Layer related problem, so PL should
deal with it.

Keeping this one as enhancement, -> OOo 2.4
Comment 9 ab 2007-11-13 16:31:14 UTC
As discussed with fl -> OOo 3.x
Comment 10 Marcus 2017-05-20 10:55:18 UTC
Reset assigne to the default "".