Also a small amount of preparation of storing parse trees instead of
linear sequences of tokens got mixed in here, namely a new type of
token called a "FUNCALL".
This change does away with separate attributes foreground and background,
opting for an array of color "aspects", where the aspect can vary
over an enum which can either be FOREGROUND or BACKGROUND. This will allow
writing a single set of color-editing code which can work either on the
foreground or background color of a cell.
Now palettes are allocated and deallocated in fteapot as well as teapot;
both executables have some color rendering, with fteapot using the cell
foreground and background (there's just no way to set them at the moment).
teapot is so far only using color in the header.
Implements #39.
Now in fteapot you can select any one of the buttons in a modal dialog
with the cursor keys and hit enter and it will be selected.
Fixes#17.
In addition, I clarified that the block attribute options will either set
every cell to bold (say), or unset every cell, or you can cancel to not
actually go through with the block operation.
These changes required adding a custom FLTK dialog, tpt_choose.{h,cxx}.
Along the way, I reflowed fteapot.fl to make it more readable for further
coding.
Finally, there is a small amount of additional prep for color support
that (unfortunately) got mixed in with these changes.
The new function is X(SRC,REF), which briefly for a cell in the neighborhood
of REF returns the corresponding cell in the neighborhood in SRC. For
further details, see the updated documention.
In developing and documenting this function, I refined some of the
existing error messages (e.g. showing the coordinates when there is an
attempt to obtain a cell with a negative coordinate) and improved the
error propagation to increase the chance that the innermost error will
percolate to the top level.
So far, this jst consists of initializing color in curses mode, and making
the display start and end part of intializing and freeing a sheet (so that
it can control allocating the palette, for example, where the data structure
used depends on what kind of display it is.
Next up will be to allocate and destroy the color palette, and set up the
default colors for cells to use (0 for foreground,
TEAPOT_WHITE for background.) The outline beyond that is to allow setting of
the cell colors, then actually display those colors, and finally edit the
palette.
In general, the goal of these changes is to be more type-specific wherever
possible, reduce duplicated code, and avoid magic numbers. The biggest
individual change is to use Location triples of integers wherever possible
rather than three separate int variables. Another very helpful change for
understanding what is going on in the code is introducing the MarkState enum
for tracking the process of marking and unmarking blocks of cell.
The MarkState change was motivated by the issues with Ctrl-C,
and this commit, in fact,
resolves#28.
Because of the lack of a test harness, it is possible that a change of
this scope has created some bugs as well, but teapot was running OK for
me at the time of the commit. However, I don't know how good my coverage of
the changed code was -- I certainly did not save or load a Lotus 1-2-3 file!
Nearly all of the basic operations in eval.c have been implemented for values
of type LOCATION. The behavior is generally modeled after typical vector
arithmetic. For "<", as a particular case, every component must be less
than or equal the corresponding component, and at least one must be strictly
less (<= drops the latter condition, of course). Note "<" returns the number
of strictly less coordinates, but 0 (false) if any coordinate is greater.
Also implements a mechanism (string array Type_Names) for printing type
information and slightly enhanced the error message for type mismatch in +
Closes#16.
In the end it turned out that the cause of the phantom values was
short-cutting in getvalue() when the contents of a cell were empty,
preventing the update of the internal cache of the value of the cell.
However, tracking this down (and getting the associated memory management
correct) necessitated implementing a debugging mode in which I could
dump the internal states of cells and print various other stuff to standard
output. It also involved understanding the meaning of various pointers in
the code, in the process of which I renamed some commonly used macros,
particularly the former SHEET(s,x,y,z) which was not returning a Sheet at
all but rather a pointer to a Cell. So this macro is now called CELL_AT. I
also replaced several very repeatedly used patterns of checking the validity
of locations and pointers with macros, now defined in sheet.h.
Therefore, unfortunately the (relatively small in the end) bugfix for this
major issue is entangled with numerous textual changes to the code made
in tracking it down.
Fixes#18.
Closes#19.
Provides additional keys to clock and reset the spreadsheet in GUI mode.
Updated LyX manual to include GUI mode keys, including the new ones, to
include some of the more recent features like bold and highlight, and
also improved some phrasing throughout.
Fixes#4.
Changes to CMakeLists.txt to allow the system fltk to be found. These may
have interfered with static linking, as now the command lines for static
and dynamic linking look identical.
A small change to fteapot.fl so that the resulting code will compile.
Some additions to the INSTALL file to help point to prerequisites.
Fixes#1.
The XDR library is no longer in the Gnu standard library, but it can be
supplied in Tumbleweed via the tirpc library, so look for that as an
option.
Also renamed README to README.md in the packaging, to reflect prior change.
