Issue 21668 - Hatching doesn't work in embedded VISIO object
Summary: Hatching doesn't work in embedded VISIO object
Status: CONFIRMED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.1
Hardware: PC Windows 2000
: P4 Trivial with 1 vote (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
: 95099 (view as issue list)
Depends on:
Blocks:
 
Reported: 2003-10-24 16:36 UTC by gregsmith
Modified: 2013-08-07 14:38 UTC (History)
2 users (show)

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


Attachments
.sxw file with embedded Viso drawing improperly renders (36.24 KB, application/octet-stream)
2003-10-24 16:39 UTC, gregsmith
no flags Details
Word DOC showing before & after (see comment) (58.00 KB, application/octet-stream)
2003-12-02 18:21 UTC, gregsmith
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description gregsmith 2003-10-24 16:36:28 UTC
.sxw doc contains embedded visio doc with
hatched areas. These display as solid on screen, printer,
or PDF export, but when the embedded object is edited, the
hatching is intact.

(can't see an 'attach file' button on this form, I guess I can
do it later)
Comment 1 gregsmith 2003-10-24 16:39:28 UTC
Created attachment 10612 [details]
.sxw file with embedded Viso drawing improperly renders
Comment 2 utomo99 2003-11-12 07:20:00 UTC
I see that all is black and not hatched. can you prof that it is
originally hatch, as I didnt have the VISIO ?

Comment 3 gregsmith 2003-11-12 23:04:37 UTC
You should be able to copy/paste the embedded
object into a W0rd doc, or pretty much anything
that allows embedded objects, where it should look OK.
I think there's a program that comes with the
dev studio which is specifically designed to
have things pasted into it so you can look at
their innards.
 
I can upload a .png of a screen shot if you prefer.

My understanding of how this stuff works is vague,
I believe this that there is VISIO data in there
and, independently, a 'metafile' which contains 
instructions on how to print/display it 
independently of VISIO. If this is case, I guess
the problem lies in how that metafile is interpreted
within OO.
Comment 4 gregsmith 2003-12-02 18:21:25 UTC
Created attachment 11703 [details]
Word DOC showing before & after (see comment)
Comment 5 gregsmith 2003-12-02 18:32:19 UTC
Turns out that what I said on 11/12 is not true. I have downloaded
the original .sxw from this issue page, and when you copy/paste
the embedded object into a Word doc, it shows up as a picture
(not a Visio object) and the hatching doesn't work. If however,
you select the object in the OpenOffice doc, use 'edit' to edit
it (requires Visio), the Visio data is displayed properly in Visio,
and can be copied/pasted from there to a Word doc, where it shows
up properly as a Visio object. 

I have attached a word .doc with both cases (copy via Visio, and
direct copy/paste). This doc was generated starting with the
OLE_Viso_problem.sxw taken from this issue page, using these tools:

OpenOffice 1.1.0
Word 2000 (9.0.3821 SR-1) 
Visio 2000 SR1 (6.0.2072) 

On my system, with Visio installed, the first object in this doc
displays properly (with hatching etc). I don't know if it displays
properly on other systems, maybe the Visio OLE server is needed
to even display the thing??


Comment 6 mci 2004-04-05 13:51:18 UTC
reassigned to mru


@ mru: Please have a little look....
Comment 7 michael.ruess 2004-05-25 13:14:39 UTC
MRU->SJ: hatching cannot be properly displayed in the object. I do not now if
its a graphics problem or an OLE problem. Please have a look.
Comment 8 sven.jacobi 2004-05-27 16:22:32 UTC
SJ->THB: Can you please takeover this issue, it seems to be a little wmf/emf
import problem, thanks.
Comment 9 thb 2008-06-27 15:31:33 UTC
@sf: please take this one back
Comment 10 thb 2008-06-27 15:34:52 UTC
Oops, wrong user, reassigning again.
Comment 11 michael.ruess 2008-10-20 16:34:45 UTC
*** Issue 95099 has been marked as a duplicate of this issue. ***