Age | Commit message (Collapse) | Author |
|
... actually only SvtFileDialogURLSelector has it.
The problem is that in this case ImplGetSeparatorX() returns 0.
Change-Id: I2f5bebce31b4f137782b5f34cc7954554af06863
|
|
Change-Id: I9ccf664e8f75a68b1b87c2b29ae617a90d0741a7
|
|
Change-Id: I5d39910647288988363751cd53f1dce6781450b1
|
|
Change-Id: Id6977932781909c81e4a5dc071f50308a58748cf
|
|
Change-Id: I278cd66fb4819721bb473796c28598aaf04eb123
|
|
Change-Id: Iad96199d00de9f739b0d003679b75510faca36f4
|
|
Change-Id: Ie1d7ed56c69539587df5310c0a1ea0476abd5542
|
|
Change-Id: Idda2852c3e96ce15fde75d5a95369ec50a012410
|
|
Those classes don't exist. So remove friend class operators too.
Change-Id: I8e3b32db933dea7cbab86015f0c926df967511f6
|
|
Part of MultiLineEdit was moved down from stvools to vcl
with name VCLMultiLineEdit. MessBox uses it to display the
message in read-only mode. Some of svtools' classes - which
are necessary to implement VCLMultiLineEdit - were moved to
vcl as a whole, and their includes are rewrite.
Note: ExtTextView and ExtTextEngine classes would be leaved in svtools
if VCLMultiLineEdit is a template class, but two macros: IMPL_LINK
end IMPL_LINK_NOARG make it impossible to use template syntax.
Change-Id: I26543868d8081c225c7125404d23369de3c3afcd
|
|
Change-Id: Ie3bb75617eef66ea5af77c8013d42a49dd69d2d0
|
|
Change-Id: I3b5865d862ac7b9958d22d2ff1d3dc693cea2536
|
|
Change-Id: Ia07c50f4822af256b3b35f39f46dc442750c8439
|
|
that is b38ee8c8d5bb10ade41d5ee4050ec4fda12fcbd2
Change-Id: Ib86d86616443cf48ba1d3ee0b6f96314b42dc972
|
|
Change-Id: Ib08bf14eebf366aa4bd3e82806a91dd12033c417
|
|
Change-Id: I6cf04b10bfdd6c7b16761b2aa2f31c1392c49546
|
|
Change-Id: If6432543c194668075b5b0a821e4bad8d7dd4839
|
|
Change-Id: Ibd749a70a7bbe8c1023edf7bd144aa6547147a12
|
|
Change-Id: I1563dc2afc49c7b1115192db00fbd08a7524154e
|
|
This reverts commit 2bc2d09bba2e3f34e8ce13571de9ff7007e1c2b6.
|
|
This reverts commit a1345cd93a57ec7d9352f2c71ec2664332ce5e76.
|
|
remove extending of pixmapRect in the nPart == PART_WINDOW branch
and simplify code, since rControlRectangle, pixmapRect and widgetRect
are the same.
Change-Id: I253851fad558e525cd533bb3576a9bba82187e53
|
|
Change-Id: I6f473c246408684c5d952a2161645e4fe76873ea
|
|
Change-Id: I73263a74d7b9bbf4a99e86773854e69f747e19d5
|
|
Still present in the framework in 10.8, so this code will continue to
link and work, one hopes... But this really is a sad "solution".
Change-Id: I2571185f412e7252887bab3e0ae02c72cd756677
|
|
Change-Id: I6a1b0ee2e7e012080774d29ea6ea5db5e9229d82
|
|
This reverts commit 0714d191e7273c3b32837834f9a37867b81cb78a.
|
|
Change-Id: I402202e199dfc8c2462859d00529f2782f6228b0
|
|
Change-Id: I011048912af051a762a78af8646513a1fc624073
|
|
This reverts commit 06d358fea294617d8618e9cf6fadb1f162fd6014.
|
|
|
|
|
|
If we blit pixels to the back-buffer, we need to remember to get them
to gtk3 at idle.
Change-Id: Ic37660e963fbbcdd132cfba0ce739174d64148d2
|
|
Change-Id: I3fabfcee9166d2b32dbadaedba6d364ae1a7559e
|
|
Change-Id: Iea44b34fbfc189c21267e095860c3bab3217bcfb
|
|
Change-Id: Iad78f62bedb93c456830b2133b67e081ab035b5e
|
|
Change-Id: Iacd8578ee71c5e0403c3398cb1f8d427be27d603
|
|
Change-Id: Ibcdc3b73b845954817f08a3f50900d96a25a8e3d
|
|
Change-Id: I46798192d019967f74e4d118b1dd322072cd3997
|
|
Change-Id: Ic77244abfc68da4b5e64d2159d5700e8ac03a999
|
|
Change-Id: I402835cf2bcdab48065eed251ba193dda6c27ad4
|
|
Change-Id: I4b01bdaf4fc20a55f2b4e9ebd039220031c03f11
|
|
Change-Id: I1fd08d94c506580ed7557066448ccb10adb9b16d
|
|
Change-Id: I739855830a7135c8e0a8d80d4f1f84e5a3901204
|
|
- bSize is not necessary
- rename bInRect to aHotspotRect
- rewrite the rectangle calculations
- fix the x-coordinate of aStartPt
Change-Id: Id474a3df5242423e5d4b6953af7e58ceeb50b810
|
|
Prior to patch hotspot and arrow symbol were being controlled by same
rectangle feature. In order to increase hotspot area but leave arrow at
the same size it was necessary to separate the two, creating a second
rectangle to control hotspot size. New rectangle named bInRect, similarly
bSize had to be created.
Change-Id: Iec27d45e1f538dc0185861be7a988b0851fbb352
|
|
Change-Id: If517926b12633a96ad8088e007cfcd6d84e5c919
|
|
Change-Id: I575dc3a4e15c88d4c61da8195ed9df6c55e5cb66
|
|
With this commit I reintroduce one pass scale, rotate and crop that
was located in grfmgr2.cxx (now in Bitmap class) and was used for
preparing bitmaps for displaying on screen. By default the combination
of two filters is used: bilinear, which is a similar algorithm than
the "old" one, but with the same result, and averaging algorithm. Bilinear
filtering is used for bitmap enlarging and shrinking till factor 0.6. Below
this bilinear gives bad results because of limited sampling. For such cases
averaging is used which is a simple algorithm for shrinking. In averaging
the algorithm calculates the average of samples which result is the new
pixel. Currently both algorithms are not optimised.
One pass scale, rotate and crop should only be used for displaying of
images.
Change-Id: I5a1330b58a7cbb6fde8546e16c3e8c140afca565
|
|
Change-Id: I8fe133dd8d1f759fbe21d47ae358c0b5451812b5
|