GitLab

Rationale (copied from htop issue #471):
The function name "setValues" is misleading. For most OOP (object-
oriented programming) contexts, setXXX functions mean they will change
some member variables of an object into something specified in
function arguments. But in the *Meter_setValues() case, the new values
are not from the arguments, but from a hard-coded source. The caller
is not supposed to change the values[] to anything it likes, but
rather to "update" the values from the source. Hence, updateValues is
a better name for this family of functions.

Two changes in this commit:
- All meters now explicitly specify "maxItems" property, even for just
  1 item. (Exception is "container" CPU meter classes, which use
  CUSTOM_METERMODE.)
- "maxItems" being 0 is now allowed. This will let bar meters and graph
  meters render an empty meter.

Signed-off-by: Christian Hesse <mail@eworm.de>

Signed-off-by: Christian Hesse <mail@eworm.de>

The MemoryMeter and SwapMeter now use the short GNU Coreutils style
format to represent memory sizes.

This is a work-in-progress, code is currently broken.
(Some actions, and notably, the header, are missing.)

See https://bugzilla.redhat.com/show_bug.cgi?id=987805 for details.
(thanks to Dawid Gajownik for the detailed analysis!)

Changes in object model: separate class objects to store vtable. Also, nicer UTF-8 display of big numbers.

Fix subtree hiding
Fix reading of CPU values in hidden threads
Fix hiding of zombie processes as kernel threads
Remove "debug proc" code
Code cleanup in processElements

Reduces resulting code size.

Avoid unnecessary operations when processing entries on ProcessList.

- add AllCPUsMeter;
- because of that, the new .htoprc is incompatible with previous released versions.