https://bugs.documentfoundation.org/show_bug.cgi?id=91328
--- Comment #3 from [email protected] --- (In reply to Noel Power from comment #2) > (In reply to Joel Madero from comment #1) > > @Noel - I think you would be most qualified to answer this one - not sure if > > anyone in QA would be comfortable doing so. > > > iiuc then this error is correct and matches what MS vba does/says (note: I > don't currently have access to any MS Office versions to check) > > There seems multiple issues described here, I wont bother trying to decipher > them, if there are separate issues then there should be separate bugs. My > response here is for the issue in the subject only, e.g. "Object Variable > Not Set" error when member not defined for Variant > > Again (iirc) this is the standard VB error in this scenario, the first > example above assigns a 'basic type' e.g an 'Integer' and a Variant > containing an Integer respectively. That type (e.g. Integer or Variant) is > passed to the 'TestVariant1' subroutine as a 'Variant' type, note: Arg1 has > no type so it will be treated as a Variant. Also Note: a Variant is an > opaque type, it's a sortof container for 'any' type you assign to it, when > you try and call a method on a Variant it 'knows' you are trying to call on > the 'Object' contained by the 'Variant' In the example above the 'Object' > assocated with that 'Variant' type is 'NULL' as the real types passed are > basically primitive types. The error reflects 'Basics' understanding of the > situation and it is telling you there is no Object associated with the > Variant. The reason why the second example gives a different error is that > 'oCurrentSelection' *IS* an object and the Variant in this case does infact > have an object instance that it tries to call a method on. If the method (or > property) does not exist for the object you are trying to call on it reports > that fact. > > I see there are other comments about the debugger stopping at the function > (implying it doesn't actually get to the real error) that sounds very > suspicious, if that is happening that would be a bug imho Okay, With regards to where the debugger actually stops, I've submitted a new bug report: https://bugs.documentfoundation.org/show_bug.cgi?id=91780 With regards to the error message itself, I was thinking of closing this off and opening a new bug suggesting more detailed error reporting for BASIC runtime errors. I appreciate the need to copy VBA's behaviour so I wouldn't suggest changing the message but I've also written a few macros using VBA and the error messages leave a lot to be desired so I think in this case it would be great if LO could go one step further and do better than Microsoft. I was thinking of suggesting a more detailed comment in addition to the error title detailing what the error means and if appropriate, giving information specific to the situation that caused the error to be generated, and/or an error code and/or a link to a help page detailing what can cause the error and what can be done to resolve it. Would this be okay with you? Thanks, stellarpower. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
