Issue 50119 - Saving bitmap palette writes o size file
Summary: Saving bitmap palette writes o size file
Status: CLOSED FIXED
Alias: None
Product: Draw
Classification: Application
Component: ui (show other issues)
Version: 680m106
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: wolframgarten
QA Contact: issues@graphics
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-31 13:03 UTC by wolframgarten
Modified: 2005-07-18 10:50 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description wolframgarten 2005-05-31 13:03:53 UTC
Open a new draw and switch to area dialog, bitmaps. Saving a new bitmap list
turns out  a 0 bytes file. 
When deleting one of the bitmaps, closing the office and reopening it again the
bitmap is there again.
Wanting to save a new standard.sob Office does not allow me to save it. Are
these single bugs or one big one?
Comment 1 clippka 2005-05-31 14:07:18 UTC
I have to evaluate this
Comment 2 kabban 2005-05-31 14:53:42 UTC
same with me here using build 104. Additional using draw my CPU goes immediatly
to 100% use.
Comment 3 clippka 2005-06-01 17:07:05 UTC
Fixed,

since the storage rework in OOo 2.0 a storage is no longer auto commited on
descrution. Therefore I needed to add a call to the Commit() method of the
storage in SvxXMLXTableExportComponent::save()
Comment 4 kabban 2005-06-16 22:31:56 UTC
with 109 and winxp the problem is still there: 0 bit long *.sob and I'm unable
to set my own bitmaps as background bitmaps. 

Example. Load an old odg with a big nice bitmap. then set the background to no
background at all, because open office wouldn't notice the change at all. import
a new own bitmap. set the new bitmap as the new background. Fine it is there.
Save the file. load the file and the very first background bitmap ist back.

And!! Loading my nice odg the cpu goes up to 90-100%. When I'm turning off the
spelling correction this does not happen.
Comment 5 wolframgarten 2005-06-17 07:55:16 UTC
Yes this still occurs because the fix is not integrated in the official builds yet.
@kabban: what you mentioned last is a new issue I think. Can you file a new
issue for it, please? Thanks.
Comment 6 clippka 2005-06-27 13:21:42 UTC
reopened and changed target for fixing on OOo 2.0
Comment 7 clippka 2005-06-28 18:05:14 UTC
fixed on cws impress61 for OOo 2.0
Comment 8 clippka 2005-06-30 14:20:52 UTC
verified in cws, back to qa

re-open issue and reassign to wg@openoffice.org
Comment 9 clippka 2005-06-30 14:21:00 UTC
reassign to wg@openoffice.org
Comment 10 clippka 2005-06-30 14:21:13 UTC
reset resolution to FIXED
Comment 11 wolframgarten 2005-07-07 14:10:49 UTC
Verified in CWS.
Comment 12 wolframgarten 2005-07-18 10:50:24 UTC
Tested in master m118. Closed.