Issue 32921 - formating in richtext control in draw doesn't work correct
Summary: formating in richtext control in draw doesn't work correct
Status: CLOSED FIXED
Alias: None
Product: Base
Classification: Application
Component: code (show other issues)
Version: recent-trunk
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: marc.neumann
QA Contact: issues@dba
URL:
Keywords:
: 35363 36440 36630 (view as issue list)
Depends on:
Blocks:
 
Reported: 2004-08-13 08:21 UTC by marc.neumann
Modified: 2006-05-31 14:29 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description marc.neumann 2004-08-13 08:21:59 UTC 
1. open a new draw document
2. insert a text control
3. open the control property browser 
4. set text txpe to multiline with formating
5. turn design view off
6. insert some text in the control and select the text
7. choose format / character
8. set f.e. strikethrough to single 
==>> the text in the control isn't strikethough
Comment 1 Frank Schönheit 2004-08-13 12:40:45 UTC 
accepting
Comment 2 Frank Schönheit 2004-08-13 13:18:57 UTC 
fs->af: The FormShellManager in Draw is created, but mrBase.GetMainViewShell
returns NULL at this moment. Thus, the manager is not properly initialized,
which means that the whole shell-switching mechanism you created in issue 25684
is broken.

Thus, the Format|Character doesn't really arrive at my form shell, but at one of
Draw's shells. Thus, the settings made there are not routed to the control ...
Comment 3 groucho266 2004-08-18 18:38:57 UTC 
Accepted.
Comment 4 groucho266 2004-10-26 13:20:24 UTC 
Fixed at three places:
1. Fixed the registration of the FormShellManager at the window of the center
pane and at the form shell to be properly informed about the activation and
deactivation of the form shell.
2. Fixed the order in which the ViewShellManager pushes the shells on the stack.
3. The ObjectBarManager::Implementation::SetPreferredStackPosition now not only
remembers the new position but moves the specified shell to that position.
Comment 5 groucho266 2004-11-04 15:58:15 UTC 
*** Issue 36440 has been marked as a duplicate of this issue. ***
Comment 6 groucho266 2004-11-04 16:37:18 UTC 
*** Issue 36630 has been marked as a duplicate of this issue. ***
Comment 7 groucho266 2004-11-04 16:40:19 UTC 
*** Issue 35363 has been marked as a duplicate of this issue. ***
Comment 8 groucho266 2004-11-09 10:04:40 UTC 
Step 1/3 of sending issue to QA.
Comment 9 groucho266 2004-11-09 10:05:17 UTC 
Step 2/3 of sending issue to QA.
Comment 10 groucho266 2004-11-09 10:05:32 UTC 
Step 3/3 of sending issue to QA.
Comment 11 marc.neumann 2004-11-10 10:59:26 UTC 
verified in cws impress16
Comment 12 marc.neumann 2004-12-10 10:30:25 UTC 
Hi,

fixed in current developer build -> close.
The current developer build can be found at
http://download.openoffice.org/680/index.html
Feel free to reopen if this issue is not fixed in the developer build.

Bye Marc