You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2013/09/19 18:29:35 UTC
[Bug 123298] New: Null pointer exception on selecting wordcount.bsh
as macro in validity
https://issues.apache.org/ooo/show_bug.cgi?id=123298
Bug ID: 123298
Issue Type: DEFECT
Summary: Null pointer exception on selecting wordcount.bsh as
macro in validity
Product: Calc
Version: 4.1.0-dev
Hardware: All
OS: Windows 8
Status: UNCONFIRMED
Severity: critical
Priority: P3
Component: programming
Assignee: issues@openoffice.apache.org
Reporter: email2akriti@gmail.com
CC: issues@openoffice.apache.org
Created attachment 81581
--> https://issues.apache.org/ooo/attachment.cgi?id=81581&action=edit
null pointer
1)Open calc-> Data menu -> Validity->Select whole number as criteria(equal to
0)
2) Goto Error Alert tab-> Select macro ->Click on Browse
3) Open OO macro->Select Word count library. Select wordcount.bsh Press Ok
4) Goto selected cell .Enter 5
Error : Null pointer exception on selecting wordcount.bsh as macro while
performing validation.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123298] Null pointer exception on selecting wordcount.bsh as
macro in validity
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123298
Edwin Sharp <el...@mail-page.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
CC| |elish@mail-page.com
Ever confirmed|0 |1
OS|Windows 8 |Windows, all
--- Comment #1 from Edwin Sharp <el...@mail-page.com> ---
As given in description.
Rev. 1523756 Win 7
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123298] Null pointer exception on selecting wordcount.bsh as
macro in validity
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123298
--- Comment #2 from Akriti <em...@gmail.com> ---
The same is observed for capatilize.bsh macro also
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123298] Null pointer exception on selecting wordcount.bsh as
macro in validity
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123298
Ariel Constenla-Haile <ar...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |CLOSED
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123298] Null pointer exception on selecting wordcount.bsh as
macro in validity
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123298
--- Comment #5 from Ariel Constenla-Haile <ar...@apache.org> ---
(In reply to Edwin Sharp from comment #4)
> Programming examples belong in help section.
> IMHO if user can't use it - don't show it in his live work environment.
Most shared macros have this nature; and as every macro, they cannot be used if
you don't know what they are supposed to do. This general rule applies to most
macros in a default user installation are like this (any category from the menu
"Tools" - "Macros" - "Organize Macros"); and the situation has been there since
the beginning.
In a normal situation, you would not execute, nor assign the macro to any
event/action, if you don't know what the macro does. So I see no reason to
remove the macros just because the average user cannot execute them.
It might be possible a small clean up (that is, remove all the code that is
only a sample, or move it to the SDK); if you agree with this, please open a
new bug.
Also note that some code must be left, for example, there are several OOBasic
functions and subroutines that might be used by extensions, or by more
power-users; in this case, the general rule applies and their cannot be blindly
assigned to an event/action; the user must know what the macro performs.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123298] Null pointer exception on selecting wordcount.bsh as
macro in validity
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123298
--- Comment #4 from Edwin Sharp <el...@mail-page.com> ---
(In reply to Ariel Constenla-Haile from comment #3)
> b) those macros are there only as programming examples
>
> This isn't a bug.
Programming examples belong in help section.
IMHO if user can't use it - don't show it in his live work environment.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.
[Bug 123298] Null pointer exception on selecting wordcount.bsh as
macro in validity
Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=123298
Ariel Constenla-Haile <ar...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|CONFIRMED |RESOLVED
Resolution|--- |NOTABUG
--- Comment #3 from Ariel Constenla-Haile <ar...@apache.org> ---
(In reply to Akriti from comment #0)
> Created attachment 81581 [details]
> null pointer
>
> 1)Open calc-> Data menu -> Validity->Select whole number as criteria(equal
> to 0)
> 2) Goto Error Alert tab-> Select macro ->Click on Browse
> 3) Open OO macro->Select Word count library. Select wordcount.bsh Press Ok
If you are going to assign a macro, you have to know what the macro is supposed
to do, be it because you wrote the macro yourself, because you know what the
code does, or because the one who wrote the macro has told you what the macro
does.
In this case
a) you are selecting a macro that counts words in Writer.
b) those macros are there only as programming examples
This isn't a bug.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.