Is it possible to modify the system colour palette?

[JÞB]

another Aero theme bug?

@ OP when Darin and Christian start debating their memories... I default to blaming Bill Gates

[altenbach]

Ah, found the important point!

It needs to be floating AND not allow the user to resize.

I had it "set allow user to resize window", causing the border to show for the floater.

[altenbach]

---

Jeff·Þ·Bohrer wrote:

@ OP when Darin and Christian start debating their memories... I default to blaming Bill Gates

---

My memory is no longer what it never was and my datapoints here are very sparse. By default, you should believe Darin. 😉

The last time I looked into window borders was around LabVIEW 4.1...5. 😄

[tst]

Some options (in varying degrees of functionality/external code combos):

1. Make the subVI float and ignore the fact that the parent will still process clicks.
2. Do the same, but set the cursor to busy before calling the subVI. This will prevent the user from doing anything in the parent, but the cursor will show as busy.
3. Do the same, but call the Windows API EnableWindow function on the parent to disable clicks in it.
4. Make the subVI modal and call GDI functions to change its size and remove the border. I'm attaching some code which demonstrates this (LV 8.0) using an ellipse. You should be able to change the ellipse to a rectangle by calling the relevant function from the same DLL. The reshaping subVIs in there come from a challenge a great but deceased LV publication (LTR) once held.

[ogebler]

@tst Yeah I have seen this solution (no. 4) however I think the time/benefit ratio is not enough for me there!

It seems the border is an element of modal operation, if you want modal you have to accept the border. However a workaround I created to simulate modal behaviour is to place a transparent colour box over the entirely of my main VI's FP, make this visible, at the front and disabled then call the subVI in floating mode. This way when the SubVI is open, you are still able to see the main VI FP parts that arn't blocked by the subVI however you are prevented from interacting with any of the main VI FP elements by the transparent box. Then immediatetly after closing the subVI, hide the transparent box again and you're back to interacting with the main VI FP. Its not exactly a beautiful solution, but I think it will provide me with both the functionality and aesthetics I desire

[ogebler]

My solution + @tst's solution no. 2 (cursor busy) works really well. A semi-transparent box to cover the mainVI, cursor set to busy to prevent events being registered on the main VI and then open the subVI. Do the reverse after closing and it works a treat. The busy cursor is actually quite useful for displaying to the user that they cannot use the main VI at that moment