Issue 17412 - You will have to restart the program - over and over
Summary: You will have to restart the program - over and over
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 1.1 RC
Hardware: PC Windows 98
: P3 Trivial (vote)
Target Milestone: ---
Assignee: drc
QA Contact: issues@sc
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-25 17:07 UTC by drc
Modified: 2013-08-07 15:15 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description drc 2003-07-25 17:07:49 UTC
Editing text within a sub generates this alert with every keystroke
Comment 1 oc 2003-08-07 11:10:51 UTC
I could not reproduce this problem. Please be a little more specific
and/or retry with the latest version (OOo1.1RC2).
Comment 2 drc 2003-08-08 14:14:23 UTC
The message arises when something goes wrong running a macro - eg 
invalid cell reference.  The macro is helpfully visible at the line 
in question, but still in 'running' state.

Any edit requiring a restart gives the alert in question - but for 
every keystroke!  Thw work-around is to uncover the error message 
windowlet that reported the macro error and OK it.  But it is tucked 
away behind the useful window....

Ideally, either:
a) show the restart alert, and allow editing to continue while the 
first alert is unacknowledged (tricky?) or:
b) show the alert once, to be acknowledged, then never again for the 
life of the hung macro process (but will the user remember...) or:
c) popup a persistent notice rather than an alert, with the restart 
warning and a 'close' button the user can ignore if (s)he chooses.

or anything else you can think of that makes more sense than one 
error message per keystroke!
Comment 3 oc 2003-08-08 14:35:48 UTC
reopened for changing
Comment 4 oc 2003-08-08 14:52:58 UTC
Hi Joerg, please have a look
Comment 5 joerg.skottke 2003-08-18 08:21:41 UTC
Hi Dr Cowsley,

can you provide a piece of code to help me reproduce the issue?
We have a similar issue (14585) and i want to make sure they are
identical.
Comment 6 drc 2003-08-19 19:09:12 UTC
Hi Joerg

I'm running RC3 at the moment.  I can't remember exactly what gave me 
the error condition, and in RC3 all the errors I can think of making 
lock me out (like my workaround option c) hence I haven't been able 
to get the message saying I will have to restart after this edit.

I've looked at 14585 and it doesn't sound quite the same, but it's 
possible there could be a common underlying problem....

At the moment, this one looks like a 'works for me too in RC3'

Chris
Comment 7 drc 2003-09-08 19:37:23 UTC
I can't reproduce it in RC3.
Comment 8 oc 2004-08-13 11:32:12 UTC
So I close this task as worksforme