- 31 May, 2018 40 kayıt (commit)
-
-
Tor Lillqvist yazdı
Written in VBScript, yay. Change-Id: Ibbdba804939c2646aef8f8a2bb3781eaf1a6d208
-
Tor Lillqvist yazdı
Change-Id: I4b0b119af356f38f359f2ba5afa6081533790443
-
Tor Lillqvist yazdı
Don't need the mbFromOLE boolean flag and the special "FromOLE" parameter passed to the InvocationService:: createInstanceWithArguments(). Change-Id: I05e10a78955d87cb7c37e198c60c3ddcfdbc4275
-
Tor Lillqvist yazdı
Change-Id: I2723146f2c549c630dfa0e5da330af228cb305a0
-
Tor Lillqvist yazdı
Corresponds to the Author attribute of css::document::XDocumentProperties. I.e. the initial creator of the document. Change-Id: I07d3ce9dfb87900948d2bb7af14109b17546fb4c
-
Tor Lillqvist yazdı
Change-Id: Ie62c47a0b60df5b7a7237cce981e850cbbe5aee9
-
Tor Lillqvist yazdı
For instance when opening a Calc Document through ooo::vba::excel:: XWorkbooks::Open(). Instead just let the function return null. It does seem that callers are prepared for that. Change-Id: I7136133155f95a696b5ed3e661a9adb98396c9c5
-
Miklos Vajna yazdı
Change-Id: I565ce46c01edfe16d5639cc62cb5a4ca996db349 Reviewed-on: https://gerrit.libreoffice.org/55098Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Miklos Vajna <vmiklos@collabora.co.uk>
-
Tor Lillqvist yazdı
Change-Id: Ic76fc43fc521a6fd6642e22b71c311370788d4aa
-
Tor Lillqvist yazdı
Enables finding out anywhere whether the thread is processing a call from an Automation client. Not sure how I have managed without this until now. Presumably the Invocation_Impl::mbFromOLE variable in stoc can be replaced by a call of comphelper::Automation::AutomationInvokedZone:: isActive(). Change-Id: Ib79ec5f6dff17af25c8539d2907c7cd5d7b9a62c
-
Tor Lillqvist yazdı
Also, it is UnknownPropertyException that we need to catch, not RuntimeException. Did I not actually exercise my change to getValue() back in February? Change-Id: If13eaa9bbecd15f5330a4102ae932f2ec0c7ecd4
-
Tor Lillqvist yazdı
Especially, this happens when an Automation client wants to open a Calc document. Equivalent to the code for the same situation in getCurrentWordDoc(). Change-Id: I209a72dcae49f18cd265e0c6c2790618e1ebb4a1
-
Tor Lillqvist yazdı
Parameters come in in reverse order in pdispparams. There might be less parameters than expected. In that case, assume the missing ones are "optional" (but can't be marked as such in UNO IDL), and fill in the rest with empty Anys. There might also be more parameters than expected. In that case, assume the oovbaapi UNO IDL hasn't kept up with added optional parameters in MSO, and just ignore the extra ones, as long as they are empty. An example: incoming parameters: <12, 13, "foo/bar.tem"> Expected paramters: (string filename, int something, int somethingElse, Any whatever, Any whateverElse) Here the existing incoming parameters are placed in reverse order in the first three outgoing parameters, and the rest of the outgoing paramters are passed as empty Anys. Another example: incoming parameters: <EMPTY, TRUE> Expected parameters: (bool flag) Here the TRUE is passed as the sole outgoing parameter, and the incoming EMPTY is ignored. Still an example: incoming parameters: <"foo.doc", TRUE> Expected parameters: (bool flag) This throws an error as the incoming non-empty extra parameter presumably indicates something important, but there is no corresponding outgoing parameter to pass it in. Change-Id: Ib04f9701099ecb899e792d99ff86588022b3bbf6
-
Tor Lillqvist yazdı
If we have too few parameters, fill with empty ones, as before. If we have more paramters than the called method expects, but the extra ones are empty anyway, ignore them. Do all of this in convertDispparamsArgs(). This improves interoperability with typical Automation clients. Change-Id: I47376993dc10b401e4c349e19b2bbe4be9f8f444
-
Tor Lillqvist yazdı
Make it easier to search for a specific class and function in the output by outputting the 'this' pointer first, not between the class and function name. Change-Id: Ia6e087e3a4be9e701c418aedb9b6af5fd4f6e828
-
Tor Lillqvist yazdı
Largely parallel to what we do for Writer. Yes, there is a fair amount of duplicated code now for the outgoing ("sink") stuff in sw and sc, that should be factored out (to vbahelper, probably). Change-Id: I8df4a81c3b9043e8d6b0b206e3c04660205987c7
-
Tor Lillqvist yazdı
Change-Id: I4d43bdd6789bdf01cd9b7b38377b19294a544477
-
Tor Lillqvist yazdı
Change-Id: I50ba5482742296609187e8b41bd3a2910c44ca4e
-
Noel Grandin yazdı
so that we flush out various code using Bitmap, in favour of using BitmapEx. This is part of the process of making Bitmap largely an internal detail of vcl Change-Id: Iaf2ead5e3d9960838723fb55b812b97108093d74 Reviewed-on: https://gerrit.libreoffice.org/55062Tested-by: Jenkins <ci@libreoffice.org> Reviewed-by: Noel Grandin <noel.grandin@collabora.co.uk>
-
Tor Lillqvist yazdı
Change-Id: Icee6f97abf9182621e43a0039b52c2f2e141fa01
-
Tor Lillqvist yazdı
Change-Id: I4360c588ee4866f4e680095c0cd0e8f7aceaa6d7
-
Tor Lillqvist yazdı
Change-Id: Ia5f8c0fcc8d1eb9f6ec3db82b947a16ed3762d01
-
Tor Lillqvist yazdı
Like the other similar attributes and methods added lately, they just forward to the corresponding attributes of the "active window". Whether setting and retrieving such then actually does something useful or not I don't know. My main concern is that Automation and COM clients at least won't complain and abort because of unimplemented APIs. Change-Id: Ia8d22e3137d314268ac6771bb355e9f0686f52dc
-
Tor Lillqvist yazdı
Change-Id: Ib230e730f68a30b82915ed6d7898bf1c02690b70
-
Tor Lillqvist yazdı
Seems to be commonly called by 3rd-party Automation (and VB6) client code. Change-Id: I29ee5e7d95f3da2ffae0fac44151148be6e272ee
-
Tor Lillqvist yazdı
It seems to be something 3rd-party VB6 clients expect to be able to get and put. Change-Id: If5079da8ba99fde74b12b9590737d575f6636210
-
Tor Lillqvist yazdı
Change-Id: I785c115ab7bcb7cfddc8e79bd5d31278f0c544dc
-
Tor Lillqvist yazdı
Change-Id: I13601337a78d22eca1df185fb4d51b34a90925f3
-
Tor Lillqvist yazdı
Change-Id: I1c706a2139cb2596969c6c1d166d3f9fe9f91d39
-
Tor Lillqvist yazdı
Change-Id: Ia2a0ade0af45f1ba99b0cfa860bd1986edcf272e
-
Tor Lillqvist yazdı
They are supposed to be emitten when a new document is created, an existing document opened, or a document is made the active document. (Hopefully our SfxEventHintId::ActivateDoc matches the last one semantically.) Change-Id: Ic53285fc3d1b9a61ababf77f06477081cef20f27
-
Tor Lillqvist yazdı
Change-Id: Ib7fcdbe934b66971995574226f982a6865faab1b
-
Tor Lillqvist yazdı
Change-Id: I428c2bbaa273d893fa5a3cc42bb7f3d060f375ad
-
Tor Lillqvist yazdı
Just call Open() with the same parameters. (Most of which are cheerfully ignored.) Change-Id: Ia9b980bf870bac04fab7e23843d29f66d5859037
-
Tor Lillqvist yazdı
Change-Id: I9c7a17aa9bdbbba29cd12a0e3d09c9047e9b5678
-
Tor Lillqvist yazdı
Change-Id: Iccdb7bc262b8f85caf7efb4407a1f00ff0cfb4a8
-
Tor Lillqvist yazdı
... Application callbacks that want to pass a such. DocumentBeforeClose() is one. (Not yet implemented.) Change-Id: I1e065d608a55e054fb41b0006a76c731915f3ebb
-
Tor Lillqvist yazdı
Change-Id: Iff629243888153250b655a5e942ced024e3338a7
-
Tor Lillqvist yazdı
Change-Id: I4a9c6341891bc80d8ab7648ed972d57739aa4f4a
-
Tor Lillqvist yazdı
The returned information for the methods is fairly bogus, though. Not sure now (a few months after I wrote the code) whether this added functionality was actually needed, or whether I just added it for potential future need, and with the intent that it needs to be improved significantly then later if actually needed. Change-Id: Ifb132f494cdd7172b4b1d05cc26e2370ea595f41
-