Feature Request: Palette Editor Input

[amforte]

If it is possible, it would be extremely helpful when interacting with the palette editor if in addition to the sliders, if there was a way to change the numbers by specifying a particular elevation value for a control point by typing a number. There are two reasons for this feature request.

1. In the case of a large dataset with bathymetry values, the inputed min and max values are extremely large. For example, a topography dataset including the open ocean and the himalayas has a min of < -6700 meters and a max of > 8000 meters. Trying to change these min and max value with sliders to useful values for most of the topography takes EXCEEDINGLY long. Thus, being able to bypass the sliders and type in a value would be nice.

2. Sometimes you want to specify a very particular value, which can be difficult to reach with slider. While the probing function allows for particular values based on points in the topography to be specified, sometimes a very particular numerical value is desired for a particular control point. For example, sea level, height of an old shoreline, estimated height of a flood, or some other threshold in the topography (minimum height of glaciers, etc). While you can get to specific values using the sliders, it can take a lot of practice and finesse. For example, it took me nearly five minutes of trial and error to get a particular dataset to simply give me a control point at exactly -27 meters, the modern height of the Caspian Sea level, and even after this amount of time I was not able to get it to exactly this value.

[amforte]

As an update, with playing more with the Palette editor, I realized that it is possible to get it to give you exact values by clicking on the line of the slider and not the actual slider itself, but it would still be nice to input numbers exactly. Or at least provide some way to move at larger increments with the slider.

[amforte]

As an another update, in theory, it seems like it is very simple to edit a saved palette file using a text editor so these problems also might be moot. It would still be nice to have a way to more precisely control the input within the palette editor menu, but in lieu of that, editing the saved palette file is a workable solution. This does require that we fix the bug where the program immediately crashes if you try to load a saved palette file...