<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN" "http://www.w3.org/TR/REC-html40/strict.dtd"><html><head><meta name="qrichtext" content="1" /><style type="text/css">p, li { white-space: pre-wrap; }</style></head><body style=" font-family:'DejaVu Sans'; font-size:9pt; font-weight:400; font-style:normal;">On Wednesday 08 April 2009, Boudewijn Rempt wrote:<br>
> On Saturday 04 April 2009, Cyrille Berger wrote:<br>
> > Hello,<br>
> ><br>
> > I have been thinking lately about the future of the dynamic brush, and<br>
> > how to improve its UI, and I have come to the logical conclusion that it<br>
> > needs to disappear. But some parts of it would need to survive:<br>
> ><br>
> > * kis_dynamic_sensor : this is a class that allow to choose which input<br>
> > events change a value (between "pressure, tilt, time, random, speed....")<br>
> > *<br>
><br>
> Yes -- something like this was projected to become part of the KisPreset<br>
> api, because we'd want store those with the presets. Also, I wanted to use<br>
> something like this to make it possible to change values using, for<br>
> instance, keyboard shortcuts.<br>
><br>
> But, as we are right now discusson on irc, this needs a bit of proper and<br>
> explicit design.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Somehow I think it is two different kind of things. We already have two ways of changing the parameters:<br>
* "static" : it is currently set with the paintop widget (I think of brush radius, fade...)<br>
* "dynamic" : changed while painting using the information from KisPaintInformation coming from mouse/tablet events<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>The sensor idea is a solution for the "dynamic" changes, and allow to use different things than pressure, and they work on KisPaintInformation. While I think the keyboard shortcuts would trigger a change in the static parameters.<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Basically, the main use case I see for keyboard shortcuts are:<br>
* increase/decrease the size of a brush without going through the widget (with +/- and/or mouse wheel)<br>
* switch between paintop pressets<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>> > Then at the top of kis_curve_option.h, I would add the selector of<br>
> > kis_dynamic_sensor, then in each kis_pressure_*_option I would make use<br>
> > of the sensor.<br>
><br>
> Probably also the brush selection option where it could be used to cycle<br>
> through brush shapes/sizes/spacing -- depending on the user's selection.<br>
I am not sure what you mean by that ?<br>
<p style="-qt-paragraph-type:empty; margin-top:0px; margin-bottom:0px; margin-left:0px; margin-right:0px; -qt-block-indent:0; text-indent:0px; -qt-user-state:0;"><br></p>Thinking of spacing, should I add a spacing slider to the autobrush ?<br>
-- <br>
Cyrille Berger</p></body></html>