Fri Jan 20, 2017 7:44 am
I'm using Hauptwerk 4.2.1 Basic on a Windows 7 Home Edition operating system. While trying to build a virtual console with the CODM, I've noticed that I can't use semi-transparent pixels on controls that change their state. I was trying to mimic a shadow for a button by a semi-transparent grey area, but each time the button is pressed or released, a new picture is just put on top of the old one, so the shadows add up to an area of increasing opacity. I'd like to add that this behaviour also defeats anti-aliasing, where semi-transparent pixels are used to create smooth borders between opaque and transparent areas, so it seems that you can't really use transparency if a control has more than one state.
I know that in 'normal' consoles, images for controls include their part of the background, so there is no need for transparency. However, I'd like to use a kit of control images with text labels that should be independent of their background.
Has anyone noticed this problem before? Is it Hauptwerk's normal behaviour or is it maybe specific to my operating system and some graphics library which is used on my system? Is it the same on Mac?
There's nothing special about it. You only have to hit the right note at the right time, then the instrument will play all on its own. -- Bach