Issue 16999 - Toolbar in IDE in wrong state
Summary: Toolbar in IDE in wrong state
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: ui
Classification: Code
Component: ui (show other issues)
Version: OOo 1.1 RC
Hardware: PC All
: P4 Trivial (vote)
Target Milestone: AOO PleaseHelp
Assignee: ab
QA Contact: issues@ui
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2003-07-17 05:31 UTC by andrew
Modified: 2009-02-05 16:18 UTC (History)
1 user (show)

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

Attachments
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 andrew 2003-07-17 05:31:05 UTC 
Create two modules in the same library.
In module2, create a subroutine that contains poor syntax such as:

Sub Main
this is not correct
End Sub

Now attempt to run the correct macro in Module1. The focus is taken to Module2
and after clicking OK to acknowledge the error, the toolbar is still configured
as though a macro is running. (The Stop icon is red and the Compile and Run
icons are disabled)
Comment 1 flibby05 2004-04-04 15:21:36 UTC 
confirmed with 1.1.1rc3
Comment 2 flibby05 2004-04-04 15:22:08 UTC 
set prio P3 -> P4
Comment 3 stefan.baltzer 2004-04-05 10:36:07 UTC 
SBA-> SW: Please take over. Thx. 
Reassigned to Stephan.
Comment 4 stephan.wunderlich 2004-04-05 14:45:59 UTC 
SW->AB: this also appears in src680_m32 and on all platforms.
Comment 5 Martin Hollmichel 2004-05-28 17:39:24 UTC 
according to the announcement on releases
(http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue
will be re-targeted to OOo Later.
Comment 6 andrew 2005-01-31 20:11:05 UTC 
the biggest problem with delaying a fix for this bug is that when it happens,
you must KILL OpenOffice because the Basic IDE thinks that it is running a macro
when it is not. You can still save and close your documents, but the IDE is
stuck and can not be closed or run any other macros. Ironically, I can still
edit the code, but I am told for each change I make that I need to restart the
macro for the change to take effect. The change is then made in the source code,
but the state still thinks that a macro is running. Even a quick hack that
always STOPS a macro when I change the macro text would suffice.

I had this problem again with the 74 dev build...
Comment 7 ab 2005-04-07 13:46:25 UTC 
ab->pitonyak: I checked this with a m86 built and found that there's only a UI
problem left. The IDE buttons are not updated correctly after you've clicked
away the error message, but if you force an update e.g. by switching to ano-
ther module, the buttons are displayed correct again. But even when the but-
tuns are in the false run state after the error, Basic isn't really active any more 
and the office can be exited normally. I hope, you can reproduce this. So I 
think, under these conditions P4 / OOo Later is ok for this task.

ab->tbe: As discussed, the problem is: The error occurs when Basic executes
its init code - including the compilation of other modules. At this time Basic
hasn't send a BASICSTART hint yet and so later also won't send a BASICSTOP
hint. Anyway the StarBASIC::IsRunning() returns true already during initialisation
and so the Basic IDE displays the buttons in running state when gaining control
because of the compilation error. You've suggested that maybe the IDE can up-
date the slot state after termination of the error dialog. I think it's better
you take
a look yourself to check this.
Comment 8 thomas.benisch 2005-12-01 13:49:30 UTC 
TBE->AB: As discussed to you.
Comment 9 ab 2006-05-22 13:41:10 UTC 
STARTED
Comment 10 ab 2009-02-05 16:12:09 UTC 
I cannot reproduce this any more on dev300 m38
-> WORKSFORME
Comment 11 ab 2009-02-05 16:18:17 UTC 
CLOSED