Issue 54750

Summary: MacroEditor dialog is listed but does not exist
Product: General Reporter: bmarcelly <marcelly.bernard>
Component: scriptingAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, kpalagin
Version: 680m130   
Target Milestone: ---   
Hardware: All   
OS: Windows XP   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description bmarcelly 2005-09-18 08:27:05 UTC
1 Menu Tools > Macros > Organize Dialogs...
2 Open folder OpenOffice.org Dialogs
3 Open sub-folder ScriptBindingLibrary
4 Edit dialog MacroEditor

You get instead dialog Highlight !
Explanation :
Dialog MacroEditor does not exist. However there is still a reference to it in dialog.
xlb file.
Comment 1 bmarcelly 2005-09-18 13:39:31 UTC
Note that this MacroEditor dialog is called by class ScriptBrowseNode in pythonscript.
py
It may be the reason of this error when starting any python script :
Sun Sep 18 14:17:20 2005 [ERROR] DirBrowseNode error: Unable to create Content! while 
evaluating vnd.sun.star.tdoc:/1/Scripts/python
Comment 2 noel.power 2005-09-19 12:43:26 UTC
np->jbu I know not what the MacroEditor is/does/was/intended to be, I can only
guess it was somthing to do with the python integration ( maybe an incomplete
attempt to provide an editor for python script-framework scripts ) unfortunately
toconnor is no longer active ( afaik ) so maybe u might know. As for the error I
would guess thats just because there are no python scripts in the active
document, I presume that this is an error message and not an error that stops
the python runtime. In the scripting project there is an xdl file, but it seems
that this is not provided as part of the install, maybe enabling that to be
packageed would be a good idea as the python script "pythonscript" uses that (
adds listeners etc ) 
Comment 3 noel.power 2005-09-19 12:50:13 UTC
"In the scripting project there is an xdl file" should say

"In the scripting project there is scripting/workben/bindings/MacroEditor.xdl" file
Comment 4 joergbudi 2005-11-06 19:43:27 UTC
Hi,

sorry for the late answer. Yes, the MacroEditor was an attempt by Tomas to add 
an editor for python scripts, but as neither me nor Tomas could spend more time 
into it, I asked Tomas to deactivate it by default (you can switch it on in the 
pythonscript.py file in the config section).

From my point of view, it can be removed, because I won't manage to spend more 
time on it.

Bye,

Joerg
Comment 5 kpalagin 2007-05-20 20:10:38 UTC
Confirming with 2.2 on WinXP - as described.
Comment 6 Rob Weir 2013-07-30 02:39:50 UTC
Reset assignee on issues not touched by assignee in more than 1000 days.