Is there a way to set the colors of the buttons to a matte color instead of the gradient color? I am using it as a color-picker, and the gradient kind of distorts the true RGB color.
Why not just use a square box? Thats what I do.
Because I don’t know how many colors I need to display ahead of time, and they can add or subtract from the “official” color choices that are available to the rest of the app at any time. So, even if I dropped 100 boxes in a container, I’d be screwed as soon as they needed 101.
So, I bind the number of allowable colors from a table (created with the real color chooser) to a multistate button, and bind the square root of the quantity to the rows, and the quantity divided by the square root of the quantity to the columns. When new colors are added or colors are dropped, the number of buttons in the grid refreshes automatically. And by binding the styles to properties from the database and ignoring the indicator value, I can have multiple buttons selected at the same time. It looks really cool and works great, except for the darn gradient color.
I can add a “Button Background 3D” property onto the multi state button like the standard button so you can have a flat background.
Thanks, that will do the trick.
Also, on a side note, is there something wrong with the ‘paste to dataset from clipboard’ in general? I can copy to the clipboard, but not paste from it. Am I doing something wrong? It happened to me with the styles on the multi state button, and another dataset on a different component.
The copy-paste of datasets seems to work for me - any hints on how to reproduce this problem?
OK, if I open a datataset, click on the copy icon, paste it to text pad, change something, copy from textpad, and then use the paste icon on the dataset, nothing happens.
Ah, thats what I suspected. It doesn’t actually work if you pass it through a text editor. The underlying reason is somewhat pedantic so I won’t bore you with it, but suffice to say that it doesn’t accept text when pasting. This would be an obvious improvement.
That would be great. I haven’t found a good reason to paste from another dataset, but it would be really nice (especially with styles) to copy the dataset to a text editor where it would be a lot faster to modify the data, and bring it back in from there.
Yeah, the tricky part about this is that when pasting from CSV, we’ve lost one important piece of information - the datatype of the columns. It would have to guess, which always rubs me the wrong way…
But, the columns already exist, so wouldn’t it already know the data type and just parse it in? All I really want to do is paste the data, not the entire dataset. Maybe you could just add a rule where you allow pasting if the column names in the clipboard match the column names in the dataset, which probably indicates that you copied from the dataset first anyway.
Anyway, I’ll shut up now. I’m just being way too picky.
Yeah, thats a good idea - use the dataset you’re pasting into as a guide, I like that.