Bug 45259 - EDITING SVG picture looks incorrect
Summary: EDITING SVG picture looks incorrect
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Master old -3.6
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-26 00:31 UTC by sasha.libreoffice
Modified: 2012-03-12 23:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
test case, try resize and change brightness (27.43 KB, image/svg+xml)
2012-01-26 00:31 UTC, sasha.libreoffice
Details

Note You need to log in before you can comment on or make changes to this bug.
Description sasha.libreoffice 2012-01-26 00:31:49 UTC
Created attachment 56169 [details]
test case, try resize and change brightness

When I opened picture from Bug 37830, I see that some problem occur, but different then in original report.
Steps to reproduce:
0. Start writer
1. insert picture from attachment by do Insert->Picture
2. try to resize this picture 
Expected: change size
Actually: always cropped
3. try change zoom
Actually: different parts of picture appears 
4. try change brightness and contrast
Actually: no change on picture, in toolbar "Color" numbers change

produced in LibO 3.6.0 master 74a356c-9eed775-f061262 on Fedora 64 bit
Comment 1 sasha.libreoffice 2012-02-20 03:02:19 UTC
fixed in 97fdf02-9eed775-f061262 (step 3)
change status to WorksForMe
Thanks for fix!
Comment 2 Rainer Bielefeld Retired 2012-03-12 22:07:12 UTC
NOT reproducible with Server installation of  Master "LOdev 3.6.0alpha0+  – WIN7 Home Premium (64bit) ENGLISH UI [Build ID: 475d0c5-829fc92-39746e8-206648e-fefd87]" (2012-02-14)

@sasha:
Can you please attach some screenshots concerning crippled view so that it will be possible to indicate regressions / duplicates?
Comment 3 sasha.libreoffice 2012-03-12 23:27:32 UTC
> Can you please attach some screenshots concerning crippled view
No. This bug was fixed shortly after creating this bugreport