Show Example/Help dialogs should be offset from wizard screens

VERIFIED FIXED in M15

Status

P2
normal
VERIFIED FIXED
20 years ago
19 years ago

People

(Reporter: robinf, Assigned: vparthas)

Tracking

other
x86
Windows 95

Details

(Reporter)

Description

20 years ago
In the CCK Wizard, clicking a Show Example button displays the Show Example
dialog, which currently overlays directly on top of the wizard screen. We should
offset the display position of the Show Example dialogs, so that they still
allow the user to view most of the wizard screen that's behind them.

Updated

20 years ago
Target Milestone: M9

Updated

20 years ago
Status: NEW → ASSIGNED
(Reporter)

Updated

20 years ago
Summary: Show Example dialogs should be offset from wizard screens → Show Example/Help dialogs should be offset from wizard screens
(Reporter)

Comment 1

20 years ago
The same behavior should apply to the help window for each wizard screen: the
Help window should be offset from the wizard screen itself.

Alternatively, should we consider making the Show Example and Help dialogs
modeless? Currently they are modal dialogs.

Comment 2

20 years ago
Bulk move to M11.
(Reporter)

Updated

19 years ago
Priority: P3 → P2
(Reporter)

Comment 3

19 years ago
Elevating to P2 to make sure we attempt to fix this.
(Assignee)

Comment 4

19 years ago
The current windows are all modal - have to decide on monday's meeting if we
need this to be so or changed to non modal.

Comment 5

19 years ago
Bulk move to post-beta1.
(Assignee)

Comment 6

19 years ago
Reassigning bugs to self
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 7

19 years ago
the SE and help dialogs are offset from the wizard screen- if you need to change
the offset or the size etc let me know and I shall do it. have changed the
offset thru the setwindowpos in the wizhelp as well as imgdlg cpp.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 8

19 years ago
Marking this Verified Fixed.
You need to log in before you can comment on or make changes to this bug.