https://bugs.documentfoundation.org/show_bug.cgi?id=170398
--- Comment #13 from ady <[email protected]> --- (In reply to Eyal Rozenberg from comment #12) > (In reply to ady from comment #11) > > This is not dependent on CF, but on SF (whether in CF or not). > > Are you saying that Excel allows SF to override DF? I am talking about what Calc does, independently of using CF or not, and with no relation to what Excel might be doing. Think about and ods file created and edited in Calc only. Are the current (DF, SF, CF) priorities in Calc wrong in some way (i.e. not working according to how they should)? (I'm not sure whether this is specified in the ODF.) _If_ there is no problem with that (in Calc/ods), then this is only a matter of import/export, and not in the way Calc prioritizes DF vs SF. In any case, by using SF and CF, users can achieve the desired result in Calc (including the case that the OP presented), even without changing anything in Calc. Then, the only remaining issue might be how Calc _imports_ (and then _exports_) these (xlsx) files when they are created with another tool (e.g. Excel). (In reply to Eyal Rozenberg from comment #12) > (I can see some counter-argument: Why would you even _have_ the early DF if > you plan for it to be overridden? Shouldn't we assume DF is post-CF, since > that's the only time it makes sense?) > > > Or consider it as freedom for the user. > > But it may well be the user who has decided to apply CF, and now we're > blocking their CF - which they probably want to apply last, see above. Please don't assume workflows and intentions of other users. We could "barely" assume some minor things when evaluating some new feature (and we would frequently be wrong). It would be unwise to assume something/anything with features that have been working in a certain way for decades, with users having a wide range of experience (from nothing to Master). -- You are receiving this mail because: You are on the CC list for the bug.
