When two abreast display was introduce, in that commit
shown below, this #define provision was also added. It
actually was an artifact left from program development
and never made much sense in a real world application.
If activated it would make the '4' toggle appear to be
broken since it would only take affect if a user first
activated individual cpu display (the '1' toggle off).
And there was no error message offered to those users.
So, this questionable #define is now being eliminated.
Reference(s):
. May, 2020 - introduce 2 abreast display
commit
59f5a37a247184b3009af963706ca68198067185
Signed-off-by: Jim Warner <james.warner@comcast.net>
w->rc.double_up = 0;
break;
}
-#ifdef TOG4_NOFORCE
- if (CHKw(w, (View_CPUSUM | View_CPUNOD)))
- w->rc.double_up = 0;
-#else
if (w->rc.double_up)
OFFw(w, (View_CPUSUM | View_CPUNOD));
-#endif
break;
case 'C':
VIZTOGw(w, View_SCROLL);
//#define THREADED_CPU /* separate background thread for cpu updt */
//#define THREADED_MEM /* separate background thread for mem updt */
//#define THREADED_TSK /* separate background thread for tsk updt */
-//#define TOG4_NOFORCE /* no force 2 abreast mode with '4' toggle */
//#define TOG4_NOTRUNC /* ensure no truncation for 2 abreast mode */
//#define TOG4_OFF_MEM /* don't show two abreast memory statistic */
//#define TOG4_OFF_SEP /* don't show two abreast visual separator */