Issue 46471 - 'Organize Macros' for python causes 'Enable JRE' dialog to pop up sevearl times
Summary: 'Organize Macros' for python causes 'Enable JRE' dialog to pop up sevearl times
Status: CLOSED DUPLICATE of issue 37020
Alias: None
Product: General
Classification: Code
Component: ui (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: joachim.lingner
QA Contact: issues@framework
Keywords: oooqa
Depends on:
Reported: 2005-04-01 11:10 UTC by
Modified: 2008-05-17 23:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description 2005-04-01 11:10:22 UTC
When I ran 'tools->macros->organize macros->python' without JRE, I got 'Enable
JRE' dialog sevearl times. However, I was still able to get 'Python Macro'
dialog and it was ok to run the macros. There seems to be unnecessary dependency
to JRE in the UI. 

Steps to reproduce

1. Open a new writer document.
2. Tunr off 'use JRE' option ( in tools->options->java ).
3. Close oo.o completely (including quick start).
4. Open a new writer document again.
5. Run 'organize macros' for python ( tools->macros->...).
6. Confirm 'enable jre' dialog pop up.
7. Click 'no' or 'cancel' until the dialog does not pop up again.
8. Choose one of macro from 'python macro' dialog and run it.
9. Confirm it runs fine.
Comment 1 thorsten.martens 2005-04-06 13:26:58 UTC
TM->CN: Please have a look, thanks !
Comment 2 chne 2005-04-07 09:25:25 UTC
cn -> jsk: just for you.
Comment 3 joerg.skottke 2005-04-15 10:28:56 UTC
jsk-> jl: This is ugly. But i believe i reported this problem before, if yes
please close one of the issues. 
The problem seems to be that the scripting framework tries to access java a
couple of times and we pop up that message at every attempt, any access to the
scriptorganizers should be affected, not only python.

Can you evaluate the issue? Should we fix this for 2.0?

Comment 4 joerg.skottke 2005-04-15 10:30:14 UTC
Target 2.0.1
Comment 5 joerg.skottke 2005-05-03 14:01:18 UTC
to jl
Comment 6 joachim.lingner 2005-05-04 12:09:01 UTC

*** This issue has been marked as a duplicate of 37020 ***
Comment 7 ace_dent 2008-05-17 21:08:24 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
Comment 8 ace_dent 2008-05-17 23:10:15 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).