Issue 15726 - Ofifce cores after user assigns script to All applications, close application
Summary: Ofifce cores after user assigns script to All applications, close application
Status: CLOSED NOT_AN_OOO_ISSUE
Alias: None
Product: General
Classification: Code
Component: scripting (show other issues)
Version: OOo 1.1 Beta2
Hardware: Sun All
: P2 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: noel.power
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-17 14:13 UTC by robert.kinsella
Modified: 2005-01-19 09:14 UTC (History)
2 users (show)

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

Attachments
pstack of core on OpenOffice.org 1.1beta2 (9.77 KB, text/plain)
2003-06-17 14:29 UTC, robert.kinsella 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description robert.kinsella 2003-06-17 14:13:14 UTC 
SFrameworkInstall.jar staroffice 6.1beta2 and OO.org 1.1beta2
Solaris sparc - error cannot be recreated on windows.

In a writer document
Select tools, scripting add ons, assign script to event.
Select a script e.g. highlightText.
Select All applications radio button.
Select Close application, select assign and ok.
Select file exit

bug - Office cores
Comment 1 robert.kinsella 2003-06-17 14:29:42 UTC 
Created attachment 6941 [details]
pstack of core on OpenOffice.org 1.1beta2
Comment 2 robert.kinsella 2003-06-18 13:37:39 UTC 
should have also stated that on windows the script does not execute on
Close application - nothing happens, the highlighttext box should be
launched.
Comment 3 noel.power 2003-06-18 14:26:21 UTC 
requires_documentation requires_documentation
Comment 4 robert.kinsella 2003-06-30 11:27:35 UTC 
setting target milestone
Comment 5 Martin Hollmichel 2005-01-18 14:42:35 UTC 
resolved/Later OOo 2.0 seems not an acceptable status, please clarify !!
Comment 6 noel.power 2005-01-19 09:13:36 UTC 
This bug relates to the original ScriptingFramework proto-type ( add-on ), we
used IZ internally for our issues. 
The state reflected our own custom handling e.g.with the add-on component we
could not address this issue so resolved in this case meant it was documented
and the target reflected it would be fixed with the real implementation of the
SF in OO2.0. So its easy to confuse this with "real" OO tasks. The SF prototype
was EOLed quite a while ago so this issue is no longer valid in anycase. ( just
to be sure, to be sure ..... I checked this with the m68 and this seems no
longer to be an issue )
Comment 7 noel.power 2005-01-19 09:14:03 UTC 
closing