office-gobmx/editeng
Noel Grandin 794d5ac4ac vcl: use enum for complex text layout constants
Since these constants are bitfield flags, we define some methods to make
working with them reasonably type safe.

Move the definitions to outdevstate.hxx, since we need the values there,
and that appears to be the "root most" header file.

Also dump TEXT_LAYOUT_BIDI_LTR constant, since it means the same thing
as TEXT_LAYOUT_DEFAULT (ie. 0), and leaving it in causes people to write
weird code thinking that it's a real flag.

Change-Id: Iddab86cd6c78181ceb8caa48e77e1f5a8e526343
Reviewed-on: https://gerrit.libreoffice.org/10676
Reviewed-by: Caolán McNamara <caolanm@redhat.com>
Tested-by: Caolán McNamara <caolanm@redhat.com>
2014-08-20 09:01:26 -05:00
..
inc drop unnecessary shl.hxx includes 2014-08-18 12:59:49 +01:00
qa WaE: overriding virtual function declaration not marked 'override' 2014-07-28 09:43:14 +03:00
source vcl: use enum for complex text layout constants 2014-08-20 09:01:26 -05:00
AllLangResTarget_editeng.mk
CppunitTest_editeng_borderline.mk
CppunitTest_editeng_core.mk bnc#467459 - fix editeng text search with expanded fields. 2014-07-27 17:06:06 -04:00
CppunitTest_editeng_lookuptree.mk
Library_editeng.mk
Makefile
Module_editeng.mk
README

Edit engine.

In OO.o build DEV300m72 this module was split off from svx but it
has no dependencies on [[svx]] (nor on [[sfx2]]) while in turn svx depends on editeng
Read more in the mailing list post:
[http://www.mail-archive.com/dev@openoffice.org/msg13237.html]