office-gobmx/sw/qa
Miklos Vajna 73ed5e3604 sw content controls, picture: add insert UI
- handle the picture case in SwWrtShell::InsertContentControl(): insert
  a placeholder bitmap & create content control around the as-char image

- expose this as a new .uno:InsertPictureContentControl command

- add the new uno command to the default & MS-compatible menus

- rename the SwWrtShell::Insert() overload taking a Graphic to make this
  a bit more readable

Change-Id: I289d6b6a9cd622c585b6cf0ec0c91d6b51ad81ac
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/134681
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
Tested-by: Jenkins
2022-05-20 16:55:16 +02:00
..
api
complex/indeterminateState
core sw content controls, picture: replace placeholder image on click 2022-05-19 14:38:03 +02:00
extras sw content controls, picture: add DOCX filter 2022-05-20 10:09:19 +02:00
inc
python
uibase sw content controls, picture: add insert UI 2022-05-20 16:55:16 +02:00
uitest Fix a UITest on Windows 2022-05-16 20:22:51 +02:00
unit
unoapi
README

You can find different types of Writer tests here, the following directories
are available:

- core:
  - filters-test: loads different file types (see SwFiltersTest::testCVEs() for
    the list of supported filter types), and only makes sure Writer does not
    crash. To add new tests, you just need to drop in the test files to the
    relevant directory, no code change is necessary.
  - uwriter: this test has access to private Writer symbols, add new tests here
    if you need that.
- extras:
  - see its own README -- executes import and export filters and asserts the
    UNO model to verify the resulting document is the expected one.
  - also, any new C++ test that links to libsw (but does not need access to
    private Writer symbols) should go in this directory, whether using the UNO
    API or the internal one.
- complex: JUnit-based tests using the UNO API
- unoapi: JUnit-based test trying to get/set every UNO property, etc.