Page 1 of 3

Search

Posted: Mon Jul 25, 2016 2:33 am
by DGDanforth
I am now getting a trap when I use Help>Contents>Search.
I was searching for "Strings".

I am using BB Version 1.7-rc1
Build Number 581
Built 2016-07-21

The trap occurs at
OleClient>Internalize>
ASSERT(res >= 0, 100);
with
res = 80070008H
res is a COM.RESULT
COM does not seem to have an interface (Is it like SYSTEM?) so I can't determine
what COM.RESULT actually is.

Can anyone else reproduce the trap?

-Doug

Re: Search

Posted: Mon Jul 25, 2016 7:11 am
by Josef Templ
I cannot reproduce the trap.

Re: Search

Posted: Mon Jul 25, 2016 7:19 am
by DGDanforth
Josef Templ wrote:I cannot reproduce the trap.
What version of BB are you using?

Re: Search

Posted: Mon Jul 25, 2016 7:25 am
by DGDanforth
I just tried it with build 589 and I still get a trap.
I am running on Windows XP
I'll now reboot my OS and try again...

Re: Search

Posted: Mon Jul 25, 2016 7:50 am
by DGDanforth
If I execute directly from the 1.7 directory then I do NOT get a trap.
If I execute out of my /USE directory then I DO get a trap.
Hence this is my problem and not a general BB issue.

Sorry to bother everyone.

Now I need to track down what is causing that.
-Doug

Re: Search

Posted: Mon Jul 25, 2016 1:58 pm
by Josef Templ
DGDanforth wrote:
Josef Templ wrote:I cannot reproduce the trap.
What version of BB are you using?
I tried it with the latest version, build 589.

Re: Search

Posted: Mon Jul 25, 2016 2:05 pm
by Josef Templ
I also checked with build 581, no trap.
There are definitely some changes in the /USE dir
that cause the problem.
Does the trap occur on all searches or only on 'String'.
Is anything related to docu searching modified in your /USE dir?
Or is there a docu file that cannot be read successfully?

- Josef

Re: Search

Posted: Mon Jul 25, 2016 10:10 pm
by DGDanforth
Josef Templ wrote:I also checked with build 581, no trap.
There are definitely some changes in the /USE dir
that cause the problem.
Does the trap occur on all searches or only on 'String'.
Is anything related to docu searching modified in your /USE dir?
Or is there a docu file that cannot be read successfully?

- Josef
o It seems to occur on all searches (3 other forms tried).
o It traps when trying to read a specific file (Physics/Docu/SparseSampling.odc).

That file uses MathType for depicting equations. Hence the trap within
" OleClient.Model.Internalize" makes sense.

Surely DevSearch should be able to handle all types of embedded material?

With GftSearchFiles a file is just a sequence of bytes and there are no limitations on the content of a file.
It does not fail when searching through "Physics/Docu/SparseSampling.odc"
-Doug

Re: Search

Posted: Tue Jul 26, 2016 8:54 pm
by DGDanforth
I just ran a test with GftSearchFiles on a file that had an embedded MathType equation.
The equation said "Hello, World!". GftSearchFiles was able to find "Hello" or "World".
That was true for whether the text was of style "Text" or of style "Math".

Hence we see that there is no need to invoke Ole and internalize the equation, at least not for MathType equations,'
-Doug

Re: Search

Posted: Tue Jul 26, 2016 8:59 pm
by DGDanforth
Josef et al,

Because of the DevSearch failure on embedded MathType equations I can no longer use
Help>Contents>Search
I have very many Docu files which use MathType.

My experiment with GftSearchFiles (see previous post) shows that searching
such files can easily be done.

I suggest that we replace DevSearch with something like GftSearchFiles.

-Doug