Bad parse from gcc-4.6.0 of...
pvfundlg.cxx: In function 'bool lclFillListBox(ListBoxType&, const com::sun:⭐:uno::Sequence<rtl::OUString>&, USHORT) [with ListBoxType = ListBox, USHORT = short unsigned int]':
pvfundlg.cxx:699:60: instantiated from here
pvfundlg.cxx:74:55: error: invalid use of 'com::sun:⭐:uno::Sequence< <template-parameter-1-1> >::getConstArray [with E = rtl::OUString]' to form a pointer-to-member-function
pvfundlg.cxx:74:55: note: a qualified-id is required
pvfundlg.cxx:74: confused by earlier errors, bailing out
GetMatrix() now returns a matrix instance even from external single
and double ref tokens. Let's use this to easily add support for
external refs to several functions at once.
Block selection with keyboard was incorrect when the selected range
included hidden cells. This also fixes one crasher on block
selection during formula reference mode i.e. type '=SUM(' and select
range via keyboard afterward.
Turns out that the token array's recalc mode is set to "recalc always"
when it contains a volatile token during compilation. We can re-use
that to mark the token array volatile before the interpretation starts.
The end result is the same, with better performance since we can avoid
re-scanning of the token array.
Signed-off-by: Michael Meeks <michael.meeks@novell.com>
When a volatile token is inside a conditional function (such as IF),
*and* the evaluation of that conditional skips the volatile token
it would incorrectly mark the cell non-volatile. The solution is
to scan through all tokens in the token array in the beginning of
the calculation and mark the cell volatile if one is found.
Turns out that the token array's recalc mode is set to "recalc always"
when it contains a volatile token during compilation. We can re-use
that to mark the token array volatile before the interpretation starts.
The end result is the same, with better performance since we can avoid
re-scanning of the token array.
When a volatile token is inside a conditional function (such as IF),
*and* the evaluation of that conditional skips the volatile token
it would incorrectly mark the cell non-volatile. The solution is
to scan through all tokens in the token array in the beginning of
the calculation and mark the cell volatile if one is found.
