Bug 33387 - Last Used category in Function Wizard can not contain functions from Add-In
Summary: Last Used category in Function Wizard can not contain functions from Add-In
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Function-Wizard
  Show dependency tree / graph
 
Reported: 2011-01-23 11:51 UTC by scren2001-pub
Modified: 2021-04-08 03:41 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description scren2001-pub 2011-01-23 11:51:08 UTC 
When using functions from the Add-In category in the calc Function Wizard, these don't show up in the Last Used category afterwards, while functions from other categories do.

Steps to reproduce:
Open Function Wizard (by f(x) symbol in symbol bar)-> Choose category "Add-In" in "Category" drop-down menu -> double click on function from "Function" list -> press "OK"
Open Function Wizard (by f(x) symbol in symbol bar)-> Choose category "Last Used" in "Category" drop-down menu -> [The function choosen before is not in "Function" list]

I used the current master, but it will probably be in any version
Comment 1 Noel Power 2011-01-24 04:28:14 UTC 
yup, can reproduce that, kohei, is this intentional behaviour?
Comment 2 Kohei Yoshida 2011-01-24 05:53:29 UTC 
Probably yes, since the Add-In functions don't have opcode values assigned to them, and without opcode values they don't show up in the last used functions.
Comment 3 QA Administrators 2015-02-19 15:39:38 UTC Comment hidden (obsolete)
Comment 4 Buovjaga 2015-03-07 14:26:50 UTC 
Reproduced.

Win 7 Pro 64-bit, LibO Version: 4.4.1.2
Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432
Locale: fi_FI
Comment 5 tommy27 2016-04-16 07:22:59 UTC 
** Please read this message in its entirety before responding **

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

Please DO NOT

- Update the version field
- Reply via email (please reply directly on the bug tracker)
- Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 

1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3)

http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug 

3. Leave a comment with your results. 

4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 
4b. If the bug was not present in 3.3 - add "regression" to keyword


Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Comment 6 QA Administrators 2019-05-14 02:53:37 UTC Comment hidden (obsolete)
Comment 7 Julien Nabet 2020-09-08 12:41:05 UTC 
Reading Kohei's comment from 2011, it seems expected.
Should it be RESOLVED/NOTABUG, RESOLVED/WONTFIX, an enhancement, other?
Comment 8 QA Administrators 2021-03-08 04:03:08 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2021-04-08 03:41:02 UTC 
Dear scren2001-pub,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-FollowUp