Y Controls

[nanocyte]

2) When you upgrade your dev env. to 2022 or when you open the project in LV64 bit, it won't ask you to resave. That save becomes a time waster when it comes to source control if you can't easily figure out that no actual code changed.

3) The latter but I do need the functionality of the former as well. I'm sure it's possible to do either. I just didn't have the patience to pick everything apart and figure it out.

[paul_cardinale]

---

@nanocyte wrote:

2) When you upgrade your dev env. to 2022 or when you open the project in LV64 bit, it won't ask you to resave. That save becomes a time waster when it comes to source control if you can't easily figure out that no actual code changed.

3) The latter but I do need the functionality of the former as well. I'm sure it's possible to do either. I just didn't have the patience to pick everything apart and figure it out.

---

Is your problem just the frame of the Y Control?

[nanocyte]

I was trying to get the background transparent so you could see the controls behind the yctl. Imagine my yctl was a round LED indicator and I was trying to hex pack them. It's quite possible I went somewhere wrong in creating them but I ended up with a gray background which would bump into adjacent controls.

[paul_cardinale]

---

@nanocyte wrote:

I was trying to get the background transparent so you could see the controls behind the yctl. Imagine my yctl was a round LED indicator and I was trying to hex pack them. It's quite possible I went somewhere wrong in creating them but I ended up with a gray background which would bump into adjacent controls.

---

The problem is that I made the template with an NXG style cluster; which can't be made transparent.  I'll fix that in the template, but of course that won't affect any existing Y Controls.  For that you can use the attached VI which converts the cluster in a Y Control to a classic style, allowing transparency.  To get that to propagate, you'll probably have to change the .yctl to a strict typedef, apply changes, then change it back to a regular typedef.

[paul_cardinale]

I just discovered a race condition in the event handler template: The state change event is passing through the state that was read before the event occurred.  You can fix existing Y Controls by expanding the unbundler in the state change event case to include all stale elements, then bundling them into the state out of the case.

I'll fix the template and the wizard in the next version.

[paul_cardinale]

---

@nanocyte wrote:

I have a bit of feedback. I'd be happy to take this offline or to another thread if that's easier.

1. I need a little more edit time magic. I wanted some way of seeing what the control would look like in place without having to run the caller. I'm thinking a shortcut menu plug-in might be a good fit.
2. Can you separate compiled code for everything
3. There were some hidden controls in the .yctl that made making a transparent control frustrating. Some of this frustration is with NI and the inability to set borders transparent. I think what I need is a seamless way to make things easy to click on at "edit" time and then more seamless and clean after you "publish" or "finalize" your control.

---

1: Try the attached menu plug-in