NOTEVIEW bugs

[flyingfisch Profile]

I have split my ebook into 40KB pieces.

Here is what happens:

I press the arrow key for next page or new line, it doesn't matter which (when it freezes at a certain spot with next page, newline gets past it when I get to that point. When it freezes with newline, next page gets past it.).

It will then freeze at certain spots in the file. But it doesn't just freeze, thats the weird part. It skips a few pages ahead, and when I go back to where I was, it freezes.


Now, I have a few questions.

Why doesn't the addin only store the current page to ram? It seems like it is storing all the previous pages to ram also.

I did not have this problem on my fx9860 with INSIGHT, which had a text reader also. Can anyone tell me why?


And, lastly, is it possible to have a "search for word or phrase" function? And maybe a way to change the pink rectangles to another color?

(Cross posted from UCF)

[SimonLothar]

I have split my ebook into 40KB pieces.

Here is what happens:

I press the arrow key for next page or new line, it doesn't matter which (when it freezes at a certain spot with next page, newline gets past it when I get to that point. When it freezes with newline, next page gets past it.).

It will then freeze at certain spots in the file. But it doesn't just freeze, thats the weird part. It skips a few pages ahead, and when I go back to where I was, it freezes.


Now, I have a few questions.

Why doesn't the addin only store the current page to ram? It seems like it is storing all the previous pages to ram also.

I did not have this problem on my fx9860 with INSIGHT, which had a text reader also. Can anyone tell me why?


And, lastly, is it possible to have a "search for word or phrase" function? And maybe a way to change the pink rectangles to another color?

(Cross posted from UCF)

I'll have a look.
NOTEVIEW's pagebuffer is limited to 0x2000 bytes. It contains only a few pages at a time and is reloaded if necessary.
There cannot be a RAM-limitation problem.

The moment I can localize the bug I will try to check, why the old fx9860-code does not fail.

After fixing the bug, I will implement a "search for word or phrase"-function.
The color-problem should be no problem.
Hang on.

[flyingfisch Profile]

Oh, I have another thing to tell you.

It seems that it does not freeze unless you turn off the calculator while you are reading and then turn it on and start reading again. Maybe something is erased when the calculator is turned off?

And thank you for working on this

[SimonLothar]

I cannot persuade the bug to pop up.
I used a textfile of 73kB size. Switched the calc on/off, scolled pages/lines up/down.
Perhaps you could send me a textfile, which usually produces the failure.

[flyingfisch Profile]

There are several files that do it.

Here is one: http://www.gutenberg.org/cache/epub/47/pg47.txt

It is UTF-8, in case that matters.

[SimonLothar]

NOTEVIEW does not support UTF-8 multibytes. It supports the CASIO-fx-multibytes, only.
Though, pg47.txt does not contain any non-ANSI chars, except the UTF-8 BOM, which is displayed as three hieroglyphs when viewed with NOTEVIEW.
To be sure, save your file as ANSI and try again, please.

[flyingfisch Profile]

OK.


And when you get "search for phrase" done, could you tell me please?

EDIT:

Does CP-1252 == ANSI?

[SimonLothar]

And when you get "search for phrase" done, could you tell me please?

sure

Does CP-1252 == ANSI?

I usually use windows notepad to save a txt-file with ANSI-coding.

BTW: I once encountered the freeze after scrolling across the 500 kB file several times up and down.

[flyingfisch Profile]

...
I usually use windows notepad to save a txt-file with ANSI-coding.
...

I use linux. :P

[SimonLothar]

...It will then freeze at certain spots...

That's a very nasty bug. But slowly I am surrounding it. Seems to be located in the vicinity of the buffer-reload-function. Hang on.