Dear All, commit 0be829e (backporting UI changes for enabling AES-256) introduced a new "slot ID" for the new option.
In file main/sfx2/inc/sfx2/sfxsids.hrc a new macro SID_ATTR_ODFENCRYPTION is defined as SID_OPTIONS_START + 100. That value is _exactly_ the same as SID_OPTIONS_END, as defined in main/svl/inc/svl/solar.hrc This means that we cannot add any more options (SID_OPTIONS_xxx) unless we increase SID_OPTIONS_END, otherwise the new options will possibly overlap with other SID's. My paranoid self would now increase SID_OPTIONS_END so we get ``room'' for more options in the future. But my paranoid self is also asking: are those Id's saved anywhere inside ODT files? Or in the AOO configuration? If we changed SID_OPTIONS_END, therefore shifting up all the subsequent Id's, would we introduce a compatibility issue with the past? The subsequent ID's are: SID_SBA_xxx SID_DBACCESS_xxx SID_RPTUI_xxx What do you think? Best regards, -- Arrigo --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
