@ oli We can't rely on background colour as that would only allow one engine to be identified at a time. As we have it, use of all engines is identified - even if one of them is only used on the last entry of a 16 part kit :)
I also thought about using colour 'patches' but if you do that after the box is drawn it covers up the text. If you do it beforehand the box wipes it, so you would have to make an empty frame instead. That then still leaves the problem of working out the X-Y positions, as they are not carried through to the function where the decision is made. Indeed, I haven't been able to work out exactly how/where they are defined :( I tried making the example ones 'inactive' but that just makes them far too faint. Oh, and not disappointing at all :) @ Kristian I tried changing to a 'down' box. It seemed to work but wasn't all that clear. An 'engraved' box looked better, but then I discovered that if you changed one, then switch to a bank that had no entry at all at that position, the 'engraving' remained. Sometimes I think FLTK really fights you :( If anyone can come up with other suggestions I'm quite happy to try them ... or even better, patches :) -- Will J Godfrey http://www.musically.me.uk Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song. ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ yoshimi-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/yoshimi-user
