Issue 66117 - Calling vFound.getString() causes statusbar reset
Summary: Calling vFound.getString() causes statusbar reset
Status: CLOSED DUPLICATE of issue 68822
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: PC Windows 98
: P3 Trivial
Target Milestone: ---
Assignee: thomas.lange
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-05 15:15 UTC by tombil
Modified: 2013-02-24 21:10 UTC (History)
2 users (show)

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


Attachments
Reset of StatusBar (9.20 KB, application/vnd.sun.xml.writer)
2006-06-05 15:17 UTC, tombil
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tombil 2006-06-05 15:15:52 UTC
Hi,
when I worked with ThisComponent.findNext...  found next mistake:
After calling vFound.getString() statusbar is reset. In OOo 1.1.5 it works O.K. 
Next basic code and attachment file demonstrate it.


sub makro1_Ctrl_M
  ThisComponent.CurrentController.statusIndicator.reset
  ThisComponent.CurrentController.statusIndicator.start("bla bla bla bla bla
bla:", 10)
  dim count as long
  count = 0 

  RpDesc = ThisComponent.createReplaceDescriptor()
  RpDesc.SearchCaseSensitive = TRUE
  RpDesc.SearchRegularExpression = TRUE 
  RpDesc.SearchString = "text"   

  vFound =  ThisComponent.findFirst(RpDesc)
  Do While Not IsNull(vFound)  
     count = count + 1
     ThisComponent.CurrentController.statusIndicator.setValue(count)

     report = cstr(count) 
   ' Calling vFound.getString() causes statusbar reset
     report = report + "   Found: "+ vFound.getString()
     msgbox report 

     vFound = ThisComponent.findNext( vFound.End, RpDesc)
  Loop
  ThisComponent.CurrentController.statusIndicator.end
  
end sub 

Thanks, Tom B.
Comment 1 tombil 2006-06-05 15:17:25 UTC
Created attachment 36923 [details]
Reset of StatusBar
Comment 2 jsc 2006-06-06 09:13:08 UTC
JSC -> TL: can you please check this, it's writer API
Comment 3 tombil 2006-06-14 20:32:14 UTC
Sorry, I misunderstand what do you wont me to check?

Described mistake I tested on Writer document (see attachment).

Comment 4 thomas.lange 2006-08-25 08:58:02 UTC
The problem is not the getString but the searching in itself.

This is another weird occurence of the problem that is already fixed by the
issue 68822.
Thus I'm setting the target to same as that issue.
This one should be fine with the next release.

*** This issue has been marked as a duplicate of 68822 ***
Comment 5 Mathias_Bauer 2007-02-05 15:46:52 UTC
going to close ancient issues
Comment 6 Mathias_Bauer 2007-02-05 15:51:08 UTC
closing
Comment 7 Mathias_Bauer 2007-02-05 15:54:33 UTC
closing