Fixed a bug involving mishandled negative offsets in
CalculationSelectableTableView::scrollToSubviewOfTypeOfCellAtLocation
and cleaned up the function.
Change-Id: I4394ca9dc9748e8b761e7f722e41014d71d3373f
responder, scroll to the bottom of the table (and not the last cell).
Indeed, the last cell might be to big to be displayed and scroll to it
might scroll to its top.
This fixes the following bug: input 1/2/3/4/5/6/7/8, OK, up, down. We
did not scroll to the bottom of the table.
When displaying a calculation taller than the screen, the output could
be displayed above the screen.
- type 1/2/3/4/5/6/7/8/9 (the main fraction between the 1 and 2)
- press UP to select the output
==> The output is still offscreen.
Change-Id: Ic3ed7664ae693d22486f8b2f9f3a8f2324c3d7c9
When scrolling to a calculation without additional outputs from a
calculation with additional outputs, the ellipsis, though invisible,
would remain selected.
Change-Id: I7408ae004b9374e432ac58361616fa2ecf1550d8
tableViewDidChangeSelectionAndDidScroll method and implement it for
Calculation::HistoryController
This fixes the following bug: In the calculation application, input 1,
OK, 1/2/3/4/5/6/7/8, OK, up, up, left, down, up. The selection failed.
The two following scenari display empty variable boxes, when there
should be loaded variables.
1) Open the console, go back to the scripts menu, go back to the
console, open the variable box
2) Open the console, execute mandelbrot, open the variable box
Scenario: +, -, / operators where no longer properly colored during
script edition.
This was due to the MicroPython update, which changed the lexer tokens
order.
We now erase the turtle before writing text. This way we can redraw it
on top of it, preventing overlapping and remanent images.
Those scripts are causing issues :
goto(-30,50)
write('coucou')
left(270)
goto(30,50)
write('oui')
-----------
up()
goto(-30,50)
write('coucou')
goto(30,50)
write('oui')
Change-Id: I01a6e5f8308937b5051165548c2046883da587d2
Scenario: Execute the script parabola.py, open the variable box, select
any leaf, enter, open the variable box again -> no variables are loaded
anymore
the object are ordered in a table. Otherwise, the compiler is free to
order them as it wants.
This fixes the test on the device: 10_m^2→_mm×_km simplifies to 10×_km×_mm
