[bt-devel] feedback

[Joachim Ansorg]

Forget this.

I was using a static lib (recheckout of Makefile.cfg).
But here are some other things I get with the correct lib:

The newperc value is sometime smaller than the perc value, this does occur if 
the range of char is exceeded (At least I think).

I get these result (have a look at swmodule.cpp for the changed messages):

(BibleTime 1.0) Debug: 74 o/o
Serious error: new percentage complete is less than previous value
using vk? yes
index: 709
highIndex: 32300
newperc ==7%is smaller than
perc == 74% 
Serious error: new percentage complete is less than previous value
using vk? yes
index: 710
highIndex: 32300
newperc ==7%is smaller than
perc == 74% 
Serious error: new percentage complete is less than previous value
using vk? yes
index: 711
highIndex: 32300
newperc ==7%is smaller than
perc == 74% 
Serious error: new percentage complete is less than previous value
using vk? yes
index: 712
highIndex: (BibleTime 1.0) Debug: CSearchDialog::timerEvent(QTimerEvent *e)
(BibleTime 1.0) Debug: CSearchDialogText::updateCurrentProgress(unsigned 
short int percent)
(BibleTime 1.0) Debug: updated current module bar
(BibleTime 1.0) Debug: CSearchDialogText::updateOverallProgress(unsigned 
short int percent)
(BibleTime 1.0) Debug: updated global bar
32300
newperc ==7%is smaller than
perc == 74% 
Serious error: new percentage complete is less than previous value
using vk? yes
index: 713
highIndex: 32300

Maybe the computation of newperc is wrong?
It's late - I'll go to bed.
Good night,
--Joachim

> Hi Troy!
>
> It seems to be impossible, but the newIndex is still 8950.
> I even changed the ighIndex part to "const long highIndex=32300", and it's
> still buggy.
> How could this be?
>
> I get these messages (I double-checked that I'm using the new lib):
> (The first message is from BibleTime and syas Sword computed 127% !!)
>
> (BibleTime 1.0) Debug: 127 o/o
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11838
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11839
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11840
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11841
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11842
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11843
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11844
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11845
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11846
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11847
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11848
> highIndex: 8950
> Serious error: new percentage complete is less than previous value
> using vk? yes
> index: 11850
> highIndex: 8950
>
>
> To show BibleTime's structure I wrote a little program called
> threaded_search.cpp, it's in examples/cmdline.
> But probably it's not a big help because it crashes (Crash occurs where
> swmodule->Search is called).
>
> It's just a quick hack.
>
> > > #5 the "search progress bug debug output" slows the search to snail
> > > speed
> >
> > I've hacked swmodule to default all vkey searches high index to 32300
> > (which is currently always true). We'll have to be sure we get this
> > working before we support multiple versification schemes, but since
> > everything is KJV numbered currently, this will work fine.
> >
> > Let me know if you still have troubles.  I'm still looking into it, but
> > we really need to release 1.5.1 and I don't want to hold you guys up
> > anymore with this issue.
> >
> > 	-Troy.
>
> --Joachim