Font size

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Start Addi

2. Press system "back" button to exit (maybe press twice, to (1) close 
keyboard, (2) leave the app).

3. Open Addi again

What is the expected output? What do you see instead?

I expected to see Addi as it was left. Instead each re-opening results in 
smaller and smaller font size, to the point it's not visible :) Forced close 
and full restart of the application starts with normal font size again.

What version of the product are you using? On what operating system?

Last (today, 13-May-11) update from Market, as well as the previous version. 
HTC Desire HD, stock firmware, Android 2.2.

Please provide any additional information below.

Original issue reported on code.google.com by dutyan...@gmail.com on 13 May 2011 at 7:52

[GoogleCodeExporter]

Don't know if it's just my phone or if everyone is having the same issues but 
scrolling also does the thing. If I scroll up&down the lineskip (ie the 
distance the lines are apart from each other) stays the same, but the fontsize 
changes during scroll and sometimes changes back afterwards. I can scroll 
left&right or tap untill I do have the desired size again. Interrestingly 
enough this does apply to input and singular value output, but it does not 
happen to a matrix output.
Not as big as an issue as not being able to see anything anymore but scrolling 
left&right is my quick and dirty fix for this issue as well and maybe these 
things have something to do with each other.
Motorola Milestone with CM7.1, but i've seen the same effect on stock 2.0 as 
well.

Original comment by DennisHe...@gmail.com on 27 May 2011 at 12:42

[GoogleCodeExporter]

Yes, the same thing is observed on Desire HD/Android 2.3

Although the originally mentioned effect with progressive miniaturization is 
more spectacular...

Original comment by dutyan...@gmail.com on 27 May 2011 at 12:58

[GoogleCodeExporter]

can you guys try again with the latest release?

Original comment by corbi...@gmail.com on 6 Jun 2011 at 4:35

[GoogleCodeExporter]

Now both effects are gone: exiting via "back" and re-opening shows the same 
font size, and scrolling does not alter font size. Thank you!

You can still get strange behavior during scrolling, if you try hard enough 
though :) For instance, if you change orientation to landscape (and screen 
reformats), now scrolling is done with very small font size. Font size restores 
to normal once you stop scrolling, but this still looks weird. After that, even 
after return to portrait orientation, small-font-scrolling behavior persists. I 
think this is in general related to screen reformatting, and same can be 
achieved with hiding/showing keyboard, but I cannot give a simple deterministic 
sequence of actions for that, while changing to landscape works 100%.

On a perhaps different note, now if you long-press the screen and get the 
standard "edit" menu (with Select word/select all/paste etc. functions), this 
menu icons are way too small, I would say twice smaller than they usually are 
in other applications, perhaps this corresponds to the extra-small font size 
seen in above-mentioned situations. Which makes the menu nearly unusable...

Original comment by dutyan...@gmail.com on 7 Jun 2011 at 7:36

[GoogleCodeExporter]

Are any of these issues still present?

Original comment by corbi...@gmail.com on 6 Nov 2011 at 3:42

[GoogleCodeExporter]

Speaking of the recent version in Market -- no, everything works fine as far as 
I tried. "custom keyboard" appears as soon as one touches the screen (i.e. you 
can't see full screen while scrolling), but I guess this is intended.

Original comment by dutyan...@gmail.com on 6 Nov 2011 at 8:05

[GoogleCodeExporter]

Also, the new version does not save screen contents between sessions (old issue 
#16).

On a different note -- why e.g. log10() is not defined (though the function is 
shown now in the "tips" line if I start entering log)

Original comment by dutyan...@gmail.com on 6 Nov 2011 at 8:09

[GoogleCodeExporter]

It isnt the most recent version, but actually the one before that made it so 
you lost your screen contents , command history etc (you must have been 2 
versions back).  This was a one time cost of being able to have add-on 
packages. 
The functions listed are all the function I should support to be Octave 
compatible.  Please file different bugs for any that either dont exist or dont 
work properly.

Original comment by corbi...@gmail.com on 6 Nov 2011 at 4:33

[GoogleCodeExporter]

Thanks. Then I guess this one can be closed (provided the keyboard behaves 
"asdesigned").

Original comment by dutyan...@gmail.com on 6 Nov 2011 at 5:02

[GoogleCodeExporter]

Original comment by corbi...@gmail.com on 6 Nov 2011 at 10:54

• Changed state: Fixed