Quote:
Originally Posted by makman94
something else that i notice (very tiny !) is that if user tries to adjust the values at RGB adjusters of your app(via num numbers) ....the side effect is that app is changing also the gradients.tga at the 'selected' area becuase both ('adjusters' and 'selected area') are using the num numbers. better to allow user changing the gradients.tga only via the 'g' button .
|
Here's how it works (or should be working):
When the app is loaded everything is using the same gradient (map, selected, and editing) and the Gradients color changer box (indicies) is loaded with colors from that gradient. If you press G to cycle through available gradients then obviously the selected gradient changes. To adjust the colors (indicies) of the selected gradient that you have chosen you have to press the load colors button. Pressing that button will change the editing gradient to the selected gradient. That will load the colors from the selected gradient into the editing colors box. Now when you edit any color index in the gradients editor box it will update the index color and also update the editing gradient so that you can see the change. To apply the editing gradient to the map you have to press the editing gradient's map button. Anytime you press the load colors button the selected gradient will be replaced and all changes are lost.
Pressing any gradient's map button will cause that gradient to be used for rendering of the map and the map will be reshown using it.
Pressing any gradient's save button will save the gradient shown in that gradient box to a file.