i.e. removal of entire call in 0f6101cfef doesn't
look right to me. That just wanted to remove the "beeps"
Change-Id: I8024c04d1e585f45fa54a82faab5f013096a708a
...as stderr is not generally visible there to the user (and vcl's
Application::ShowNativeErrorBox might not yet be functional during early start
up).
Change-Id: I1b99a77f7add967579d726462aa0a7b83a5d2d0a
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
...the new cppuhelper/source/defaultbootstrap.cxx now forbids this nonsense with
a PropertyVetoException. It looks like the code in propbrw.cxx had always been
confused about what to do exactly (using xOwnContext as delegate in the call to
createComponentContext should just be enough) and the useless re-setting of the
global ServiceManager's DefaultContext happened to work by accident.
Change-Id: I80a87fe9b0948d9aa6dc9e2e63497097044a4959
In Base:
1) Open a big table (hundreds of rows)
2) Only the first 40 to 100 rows are fetched into the cache and shown
(depending on screen / window size).
3) Move to last row (click on icon |>|)
4) The last 40 to 100 rows are fetched into the cache; the data of the
first 40/100 rows is pushed out of the cache.
5) The first 40 to 100 rows are fetched, just so that the call to
rWindow.Paint() can do its job, because they are not in the cache
anymore (!). The last 40/100 rows are pushed out of the cache.
6) The last 40 to 100 rows are fetched into the cache and displayed;
the first 40/100 rows are pushed out of the cache *again*.
Steps 5 and 6 are obviously *very* stupid.
Change-Id: Ic11b893ea9440c2c5a142bd3c77c95d6730aa723
This prevents a crash on exit for INTERCEPT=demo but there is another:
Open more calc documents, close one, and then type something -> crash.
I wonder if this was working in the past.
Change-Id: I599b1babb02488d317c6684aba7431b5de7af15b
This is a follow-up bandaid for fdo#48096 side-effects, which in
turn was a band-aid for side-effects caused by ooo-build's
toolbar-decorations-svx.diff.
Fix instructs vcl to not auto-close the floater on losefocus events,
which at least on OSX comes _before_ we even see the mouse button
down event.
Change-Id: I21896c4169addffdf2af920a37e0e3786438cc4e
