From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
In the current project context, that color change would/should indicate a new file type.
Where else in the project does a color change indicate a new file type? I see it more like this:
picture indicates the file type
overlays convey additional information (e.g. locked)
color is used by the programmer
AQ Wrote:
I hope someday to add interfaces, traits and generic/template classes to LabVIEW. Won't happen any time soon, but each of these would likely be some sort of colored cube.
Interfaces and traits could be represented by overlays on the cube, and a generic/template class could intuitively be shown as a wireframe cube. I don't see those additions as preventing an alternative use of color.
> Where else in the project does a color change indicate a new file type? I see it more like this:
picture indicates the file type
A change in the color is a change in the picture, as far as I'm concerned. It's not the same picture if it's a different color. I'm listening to the discussion here because I'm open to changing this, but I don't think viewing any change to the image as equivalent to changing the image is that unusual.
> Where else in the project does a color change indicate a new file type? I see it more like this:
picture indicates the file type
A change in the color is a change in the picture, as far as I'm concerned.
OK, substitute the words "the particular object (not the same as an OOP object) which is drawn (but not including its color)" for "picture" -- it's just semantics. I still cannot think of an example (in LabVIEW or elsewhere) where a new file type is conveyed solely by a color change. So if the underlying contribution of this idea is the statement "change in color != change in picture", then I'm all in favor*.
* Always bugs me not to be writing colour and favour!