GitLab

The variable 'dot' in GraphMeterMode_draw now means "maximum number of
dots per value (column) in graph". The old meaning was "amount of value
that is to be represented by a dot" and was always a fraction. Due to
a limitation in floating point computing, if GRAPH_HEIGHT were not a
power of 2, then rounding errors will occur on numbers like (1.0/3).
(Currently GRAPH_HEIGHT is 4 and so no precision loss.) 'dot' was used
as a divisor, and it's "division by a reciprocal". We change that to
simple multiplication.

This allows the graph be rendered with a differ color scheme when user
changes the color scheme.

This patch colors the graph meter based on the items of the bar meter.
For example, if most of the CPU power is running on low-priority
processes, then blue will be shown on the graph columns. If most of the
CPU is running on kernel things, then the columns will be red, and so
on.

The algorithm in this patch is not final yet. Expect some bugs such as:
that some of the cells are colored gray while ideally they shouldn't.

Currently GRAPH_HEIGHT=4 . This prevents hard-coding the height of the graph meters, and allows user to change it at compile-time.

(It's still unchangeable in runtime yet. Can a Setup option be implemented for this thing?)

major meters update

Fix text on function bar when moving meters.

Before:
[Up]Up [Dn]Down [Lt]Left [Rt]Right [Arrow]Confirm [Enter]Delete [Del]Done

After:
[Up]Up [Dn]Down [Lt]Left [Rt]Right [Enter]Confirm [Del]Delete [Esc]Done

this caused htop to show processes as if freebsd kernel was their parent.
on next pass reparenting code took chance to run, and that caused process to jump around.
this fixed behaviour should be the correct one

Redraw the panel when resizing the window during an incremental search

KEY_RESIZE wasn't handled by the incremental search. Resulting in this
bug:

  * Set your terminal window to a small size.
  * Press '\' to filter the processes
  * Maximize your terminal window
  * The list of processes didn't resize.

This change fixes this bug.

Thank you Julian Andrews (@julianandrews) for finding this bug.

See #198.

when testing for ncurses library. See #198.

Update calculation of used vs. free memory.

Ensure that all necessary libs and flags are passed along,
such as adding -ltinfo when needed.

Closes #198.

Thanks to @OmegaPhil for discussion and reviewing.

reclaimable slab as cached memory.

Hopefully this presents a more truthful representation of
available vs. used memory on Linux.
See brndnmtthws/conky#82, #242, #67, #263.

match load averages description to what it actually shows

Manpage update

Integrate Travis-CI

Add Darwin swap meter