Issue 7003 - No screen-update after unlockControllers
Summary: No screen-update after unlockControllers
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows 2000
: P3 Trivial
Target Milestone: ---
Assignee: chne
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-08-15 12:53 UTC by martho
Modified: 2013-02-24 21:09 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 martho 2002-08-15 12:53:51 UTC
oDocument = oDesktop.loadComponentFromURL("file:///"+sDocName, "_blank", 0, 
mArgs) oDocument.lockControllers()
... do some replacements in the document
oDocument.unlockControllers()
(StarBasic-Code)

The problem: After that I often have some "rubbish" on the screen, showing the 
original text of the document on some places and the replaced text on other 
places.
Comment 1 ooo 2002-08-15 14:47:12 UTC
implementation issue
Comment 2 thomas.lange 2002-08-16 08:34:34 UTC
accepted.
Comment 3 stephan.wunderlich 2002-08-16 10:37:30 UTC
I couldn't reproduce this behaviour with OpenOffice.org 1.0, maybe 
some further information about
 '... do some replacements in the document'
would be helpful.
Comment 4 martho 2002-08-16 10:42:36 UTC
sKeys is an array. sValues is an array. sKeys(i) should be replace be 
a sValue(i). There are about 400 Pairs to replace. The "rubbish" 
appears only sometimes and vanishes when the window is redrawn by 
some cause.

for i = LBound(sKeys()) to UBound(sKeys())
	' Replace Text
	oReplace.SearchString = "<"+sKeys(i)+">"
	oReplace.SearchCaseSensitive = FALSE
	oReplace.SearchWords = FALSE
	oReplace.ReplaceString = sValues(i)
	oDocument.replaceAll(oReplace)
next i
Comment 5 thomas.lange 2002-10-23 14:32:55 UTC
TL->CN: I could not reproduce this with OO 643 E or current SO srx 
644.

Maybe a bugdoc with macro would be helpfull.
Comment 6 chne 2002-10-30 13:23:44 UTC
cn->martho: I could not reproduce this behavior. Please can you attach
a bugdoc, means a document including basic macro? Otherwise I need to
close this bug without any fix.
Comment 7 martho 2002-10-30 14:56:36 UTC
martho->cn: I couldn't make a macro which reproduces the behavior 
100%, not even 1%. It's in daily work that the behavior appears, in 
about (*wild guess*) 1 time of 500. We are calling the basic marco 
via DDE from a C++-App, perhaps OO has to be closed first to get more 
chances to reproduce it.

My intention when I started the issue was that it's a generall fault, 
but it doesn't seem to be.

So my suggestion is to close the issue. If I get a reproduceable 
version, I will reopen it (if this is possible) or make a new one.

Thanx for your afford!
Comment 8 chne 2002-11-11 10:24:57 UTC
CN: close this task
Comment 9 chne 2002-11-11 10:25:24 UTC
CN: close