Age | Commit message (Collapse) | Author |
|
For a non-placable WMF image the size is unknown and needs to be
calculated by using a bounding box over all elements. Sometimes
this results in a very big image which is not drawn correctly
when using dashes and dots. This change normalizes the size to
reasonable values.
Change-Id: I0e5b71fb011c5a9dff1c5cb13e29d5578570ca65
|
|
This reverts commit 17ca93a6e592d3109e47c756fcfe8ac975acae5f.
|
|
Change-Id: Ia779045d93361a4ca4bfe5027958a04fdebd2ca1
|
|
Change-Id: I00b06d1330241c4df3b07dc6e0019c49fd7aa521
|
|
Change-Id: I9cc9bfbddd3a90e00eee3e674994e5d6207f9034
|
|
Change-Id: I4a92c66892fbb9687b9e7c521c770150b75229b0
|
|
Change-Id: I3392294f8144a9f3124ada972934bb0452c6e13b
|
|
Change-Id: I55cbab29e4e0d772e593f39ba48a3a2dffbce382
|
|
Change-Id: I551901111ee8eee2a9c1cf75890b89f7100d925d
|
|
Change-Id: Iff26673bd97827bca20b19937591c1fbc69bdf4f
|
|
Change-Id: I90b3c0369a54c22a87bd660801b5ea384e01c19a
|
|
Change-Id: Iaf48a39fa1d4d7b88143022e517f2c4e119e94d5
|
|
Change-Id: I8c597e5b9049cd23223ecf4376a4449ca1effb38
|
|
Change-Id: I0d0336f4f3a7add0f11f7b8d19aec517c3d8c9af
|
|
Change-Id: I6721e78f8a10d95a54ff09c1f25f0ae3ece71cfa
|
|
Change-Id: I04bf1470e43ed08ef5759fcbd6f96d4896f7690b
|
|
Change-Id: Ia817fbe4aa2927ac5568fd842e8f313608bed320
|
|
Change-Id: I3b1f63d280549ca0dc3ec59733fa6e9ca2672a1c
|
|
Change-Id: I61a366f4dd005cb19794b48c857760a3b2a8a267
|
|
Change-Id: I98076c6e23b69b2e59dcca9fbc35a3a9755e564c
|
|
Change-Id: Ia6752c8ab95fc5dc9846c939d1f8767f17f6ced6
|
|
Original behavior was to call DrawBitmap without the size argument.
case IMAGETYPE_BITMAP:
{
const Bitmap &rBitmap = *static_cast< Bitmap* >( rImage.mpImplData->mpData );
if( nStyle & IMAGE_DRAW_DISABLE )
DrawBitmapEx( rPos, makeDisabledBitmap(rBitmap) );
else
DrawBitmap( rPos, rBitmap );
}
break;
A check of bIsValidSize is needed here, too.
This brings the missing bitmaps back.
Change-Id: I60582090a7543b3916b15675af1a5ec9ee216270
|
|
Change-Id: Ie95fe7f64e9f60500748511aa1e55c430f0a6641
|
|
Change-Id: Iaab1985c5db6482578d66abf224248da38db1624
|
|
Change-Id: Ia570a267732a4f7d76f1873563f6db1eb884dc56
|
|
Change-Id: I729eab07b6de04be07e8495f28d14bcf1191e00d
|
|
Change-Id: I8f817ba8fc286979f666ad06f4fe21f4703b4652
|
|
Change-Id: I71edb2768d24f0c6686a9c94333447a5acc498b4
|
|
Change-Id: I259f3a192097fed449bbea28a18febccfd93db04
|
|
Renamed functions:
+ supportsOperation -> SupportsOperation
For consistency
+ DrawAlphaBitmap -> DrawDeviceAlphaBitmap
I want to make it more clear that these are the functions that call
on mpGraphics to actually draw on the graphics device
Change-Id: Ic4951bfcc0ac0c09fe5b6908dfdf1f699a634265
|
|
Change-Id: I7355db3294f5aaa3b4f4bac802ba064724ad2214
|
|
Change-Id: I7dbd9ec79213d43acf6486a2507c8f0cfb47d943
|
|
Change-Id: I01c0974d3a2f79cf3c6b9730ea306dcd49927a3c
|
|
Change-Id: Ie49b5b2c489619700f9cc34d9efb38454bcaff2c
|
|
Change-Id: I98977212547929ff59641f0b73273d68740420fd
|
|
I have rearrange the various functions of OutputDevice to better group
them in outdev.hxx. Also moved ImplRotatePos and ImplDrawWavePixel into
the OutputDevice class.
Change-Id: I0b384a4d094dffcfb3ee19c29562630cfb3a2167
|
|
Change-Id: I8eace414ba07c188e435aa693331a60cf2aec246
|
|
Change-Id: Ice7a07337397d9808580c626df023fe39f535651
|
|
Plus some cosmetics
Change-Id: I42d989217a0b40a8a6a03c0ebc6c4aa14b34d387
|
|
Change-Id: Ibb7178330d356806cea2cfc972b361167d5a9340
|
|
Change-Id: I618dacceb88ddab1ca6d45a8669199354e4b6a6d
|
|
Change-Id: I7a0ceee6c784af8240fb908f19622d4ede1f5a6a
|
|
Change-Id: I967a50cf4fdde87efbcec990eab4f68570f27b94
|
|
Since the tests are run during LO startup, this is not such a good idea.
Also redo the socket notifier test which seems a bit of an overkill
when a mere pipe will do (and I'm not sure TCP sockets would have
the data available the moment it's written to).
Change-Id: I6a436b286d20ceecf859f9028af98da03c2561b7
|
|
should not be virtual then prior to 95711f5b9e7b6a982d1762d37d5a38e0f40b86f9
the menu ImplInitClipRegion had nothing to do with the outdev
ImplInitClipRegion and so all the original ImplInitClipRegion calls here should
now be routed to InitMenuClipRegion which was removed by "In fact
InitMenuClipRegion() is unused" so restore that
Change-Id: Id208b30561803ee774e10d44e19ed0808f824766
|
|
Change-Id: If2c5d406994902839c4c81a947fc46a06056fe90
|
|
Dash length, dot length and distance also need to be world
transformed to be compatible with device metrics.
Change-Id: I57c04f5010006aaf8c1c32e0949cb39b7f2bc67d
|
|
Change-Id: I5198baeb7b396bec2df991a94a57531f35b7a24b
|
|
Specific to KDE4 vclplug and just a bit of a hack, but it's at least something.
Change-Id: I4bf0f9c8e0b4f7faebaf010a06fcc4ff2e44fa6b
|
|
When OutputDevice's ImplInitClipRegion got marked as virtual, the
compiler raised a warning about colliding method names in
MenuFloatingWindow, and this got fixed by making the method virtual. But
making it virtual just makes the warning go away, doesn't fix the real
problem, that OutputDevice's ImplInitClipRegion() is no longer called,
leading to strange missing text in the menus.
In the meantime also ImplInitClipRegion() got renamed to
InitClipRegion(). Fix the problem by renaming InitClipRegion() to
InitMenuClipRegion() in MenuFloatingWindow.
Regression from 95711f5b9e7b6a982d1762d37d5a38e0f40b86f9 (fdo#74702 Move
ImplInitClipRegion Window code out of OutputDevice, 2014-04-25).
Change-Id: Ibeb5e8e99bf4369b349ac44376a2c217786ef318
|