https://bugs.documentfoundation.org/show_bug.cgi?id=155112

Julien Nabet <serval2...@yahoo.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |caol...@redhat.com,
                   |                            |serval2...@yahoo.fr

--- Comment #1 from Julien Nabet <serval2...@yahoo.fr> ---
I gave a try to this one, thought it would be not too hard but the whole
mechanism doesn't use usual ui Glade file, welding process, etc.

If someone is interested, here's some code pointer:
#0  pcr::(anonymous
namespace)::EnablePropertyUIElement::updateUIForKey(rtl::OUString const&, bool)
const (this=0x7f757589fbc0, _rKey="Type", _bFlag=true) at
extensions/source/propctrlr/composeduiupdate.cxx:512
but since I failed to see where we may disable the entry associated to the
label, perhaps it's not the right one.

Caolán: just for curiosity, do you continue the welding process or this kind of
remnant would be far too long to convert?
I mean with a usual mechanism, I'm quite sure it would have been easy to fix.

BTW, locally I used g++ -E to convert extensions/source/propctrlr/formmetadata
since I was stuck just searching about RID_STR_XSD_WHITESPACES
git grep -n RID_STR_XSD_WHITESPACES
extensions/inc/strings.hrc:212:#define RID_STR_XSD_WHITESPACES                
NC_("RID_STR_XSD_WHITESPACES", "Whitespaces")

after conversion, there's this extra line:
extensions/source/propctrlr/formmetadata.cxx:159:        OPropertyInfoImpl(
PROPERTY_XSD_WHITESPACES, PROPERTY_ID_XSD_WHITESPACES, PcrRes(
RID_STR_XSD_WHITESPACES ), 55, HID_PROP_XSD_WHITESPACES, PROP_FLAG_FORM_VISIBLE
| PROP_FLAG_DATA_PROPERTY | PROP_FLAG_ENUM )

that's why I hate the preprocessor macro programming, preprocessor should be
just to deal with include file or system specificities (little/big endian)

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to