Not sure this is a bug exactly, but it's an inconvenience.
Re-sizing the GUI changes the increments by which parameters update when you drag a knob. This seems strange in general, but it's specifically a problem for some parameters where you often want to hit integer values.
For instance, VCO and LFO pitch knobs travel through these values when the GUI size is "normal": 0.00, 0.20, 0.40, 0.60, 0.80, 1.00, 1.20, 1.40, 1.60, 1.80, 2.00, ...
That seems good.
But when the GUI size is "large," you get a different sequence of values: 0.00, 0.13, 0.27, 0.40, 0.53, 0.67, 0.80, 0.93, 1.07, 1.20, 1.33, 1.47, 1.60, 1.73, 1.87, 2.00, ...
That's not so good, since you have to shift-drag to hit integer values like 1.00 and 3.00. (As a side-issue, the rounding is slightly different if you start high and drag down: 2.00, 1.87, 1.74, ... but that's unimportant.)
Similarly, when the GUI size is "small," you have to shift-drag to hit integer values that aren't multiples of 4.00.
A little issue with re-sizing ACE...
-
- KVRian
- 1184 posts since 13 May, 2004 from SF Bay Area, California
If you like 80s retro sounds, check out my latest tune…
-
- KVRAF
- 4197 posts since 23 May, 2004 from Bad Vilbel, Germany
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
That's problematic, I would need to add higher resolution bitmaps at twice the size or so...zvenx wrote:sorry to jump on your thread but if he is fixing that, I would also like the gui to be less blurry at larger sizes.
rsp
-
- u-he
- 30216 posts since 8 Aug, 2002 from Berlin
Not really, but I have to add some logic that selects the same bitmap graphics in the right resolution.zvenx wrote:does this mess with the memory requirements of the plugin?
But of course, it would use up more RAM for higher resolutions.