Difference between revisions of "Adding new sorting key"
Jump to navigation
Jump to search
(Initial version of the page) |
(Describe why it's important to add new elements to the end.) |
||
Line 1: | Line 1: | ||
− | # Update <code>SK_*</code> items in <code>ui/ui.h</code>, that is add new value to the end of the list and update <code>SK_LAST</code>. | + | # Update <code>SK_*</code> items in <code>ui/ui.h</code>, that is add new value to the end of the list and update <code>SK_LAST</code>. New elements should go to the end because otherwise they will break restoring sorting keys from <code>vifminfo</code> files. |
# Compile errors will show arrays/switches that need an update (with <code>-Werror</code>, just configure as <code>./configure --enable-developer ...</code>). | # Compile errors will show arrays/switches that need an update (with <code>-Werror</code>, just configure as <code>./configure --enable-developer ...</code>). | ||
# Note that order in sorting dialog differs from enumeration values and is mapped to them via <code>indexes</code> indirection array in <code>modes/dialogs/sort_dialog.c</code>. | # Note that order in sorting dialog differs from enumeration values and is mapped to them via <code>indexes</code> indirection array in <code>modes/dialogs/sort_dialog.c</code>. |
Latest revision as of 16:19, 13 August 2015
- Update
SK_*
items inui/ui.h
, that is add new value to the end of the list and updateSK_LAST
. New elements should go to the end because otherwise they will break restoring sorting keys fromvifminfo
files. - Compile errors will show arrays/switches that need an update (with
-Werror
, just configure as./configure --enable-developer ...
). - Note that order in sorting dialog differs from enumeration values and is mapped to them via
indexes
indirection array inmodes/dialogs/sort_dialog.c
.