Travis Ralston f141ee1944 Use the correct level order when getting arbitrary settings
This shouldn't currently be causing problems, but will in teh future. The bug can be exposed by having a setting where the level order is completely reversed, therefore causing LEVEL_ORDER[0] to actually be the most generic, not the most specific. Instead, we'll pull in the setting's level order and fallback to LEVEL_ORDER, therefore requesting the most specific value.

Signed-off-by: Travis Ralston <travpc@gmail.com>
2017-11-15 19:24:32 -07:00
..
2017-11-01 11:30:25 +00:00
2017-11-07 11:27:42 +00:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-10-27 16:29:56 +01:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-11-12 00:00:46 +00:00
2017-10-11 17:56:17 +01:00
2017-10-11 17:56:17 +01:00
2017-10-24 18:32:50 +02:00