Apache OpenOffice (AOO) Bugzilla – Issue 68902
VBA: Needs to determine all cells have same content
Last modified: 2013-02-24 21:00:30 UTC
Some attribute/properties of a Range object return as null if not all the cells in the range contain the same value. In the Openoffice.org ScCellRange uno object these values typically have a default value if all cells do not have the same value. ScCellRangesBase returns the properties based on the SfxItemSet for the range, normally a state of SFX_ITEM_DONTCARE indicates that the value of the item in question changed across the range. ScCellRangesBase however applies ClearInvalidItems() to the SfxItemSet ( which fills those values with defaults ). This patch modifies ScCellRangesBase so that its possible to determine whether these values are the same across the range or not it does that by simply maintaining a copy of the SfxItemSet ( that hasn't had ClearInvalidItems() applied to it )
Created attachment 38739 [details] patch file
trying->DR ( again & again ) again needed by vba api ( which uses the ScCellRangesBase object directly )
ooops
target/started
utomo99
change to patch ->dr maybe npower8 would be a good place to put this in? I am happy to make the changes if you are happy to accept/review/suggest etc..
I have added this to npower8, this is imo a pretty non intrusive patch, hope you agress
yes, I agree, looks good
change target, reassign to me..
changed component
fixed
->qa
attaching a document that tests the font attribute of a range, e.g. if for the whole range the Bold attribute is the same then you get that value, if one of the cells in the range has a different Bold attribute then Range("a1:c2").Font.Bold will return a NULL. Attaching a document to test that
Created attachment 49791 [details] test document
with the vbaapi.oxt extension installed open the document and press the button, the result should say "passed"
Passed Regression testing on SLED10SP1 using vbaapi-patched.oxt and on Windows using vbaapi.oxt.
This issue is closed automatically and wasn't rechecked in a current version of OOo. The fixed issue should be integrated in OOo since more than half a year. If you think this issue isn't fixed in a current version (OOo 3.1), please reopen it and change the field 'Target Milestone' accordingly. If you want to download a current version of OOo => http://download.openoffice.org/index.html If you want to know more about the handling of fixed/verified issues => http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues
Created attachment 74000