ShaunR

Check the project XML and see if there are any absolute paths rather than relative paths.

Setting "Verify" to false just turns off the certificate check so that any old certificate is accepted without error. This is of course a security risk and should never be used outside of development. IIRC. The LabVIEW HTTP functions use cURL and the "ca-bundle.crt" located in \National Instruments\Shared\nicurl. It contains the certificates of the Authorities. Adding the servers' certificate or the servers' trusted root certificate to that list once you have ascertained the certificate is correct for that website; is the recommended procedure for adding ad-hoc certificates (thus keeping "Verify" = True).

I only see a 1d array of images loaded from files (which you didn't post). Is the question to convert the 1D array of image files into 2D? How to stitch a 2D array into a single image that looks the like 2D array (stitch row, by row, column by column)? How to stich the images of a 2D array into one long image? (Vertically, horizontally?). If I were to "stitch" some images together, I would use the default Picture Toolkit or maybe Vugies Bitman library rather than the Vision Software. Here's an example using the Picture Toolbox, which loads a number of *.png files, splits them into a 2D array, then "stitches" them together as one long horizontal image. It should be fairly straight forward to "stitch" by rows or columns from this point, if it is required, by adjusting the Top/Bottom in the same way. Multiple row stitching.vi

Is Cirrus Logic part of NI?

That's probably after unchecking "place terminals as icons" and is what I shout when disabling the 32&64 bit Web-servers that NI installs (that I didn't ask for)

Yes. I set this value in the options (Front Panel>>General>>Open the control editor with double-click) and was able to open the button in a separate editor window by double clicking on it in "customise mode"

There must be another step or perhaps an ini-key because customise is greyed out for the browse button on my installations.

Really? I didn't find it difficult or onerous at all - just case statements for edit and run-time behaviour. With xControls, everything takes a lot of programming to get the basics, hence why your toolkit has a place (which it excels at, by the way). But once you have the basics of updating/drawing/refreshing the display (the hardest part), creating edit-time functionality isn't difficult. - mainly menu manipulation. In fact. Because front panel menus are mainly used to configure a control at edit-time and you can add in-built menu options to a custom menu; inheriting functionality from the architypical control (like enable/disabled/greyed out) isn't a problem and doesn't have to be re-implemented as it does with the diagram properties and methods.

I've no interest in NXG. When LabVIEW finally dies, I will use one of my other languages that supports x-platform.

Well. NI have never really worried about finding a way out of a corner - I'm still waiting for unicode support but I take your point. If NI see this as fullfilment of an issue, the 11 xControl bugs currently in the known bugs list will never be fixed.

Oh. On this point. I'm currently struggling with the "dirty vi" propblem. If I set the state to changed, the VI it's used in wants to be saved (even though nothing has changed). If I don't set the state, the control won't update the facade.I can live withthe dirty VI but "Level where general public would find it useful" is just out of reach.

I don't think it matters. If it's a package that comes with LabVIEW, you can choose to use it or not.

A hooovahh said. They do but it's really only a wizard that takes the grunt work out of creating the properties and methods yourself (something xControls could have done and probably still could do). I think rather than thinking as it being an alternative. Think of it as a run-time only package. There are no edit time capabilities and it isn't encapsulated like an xcontrol. It would have been useful for my Markup String xControl if a little unweildy for the end user (they would have had to have init and deinit Vis and an event structure instead of just placing a control). But It wouldn't have been much use for my Tab Control as that needs edit time capabilities and doesn't inherit from any existing control. I see it has a place, but it doesn't seem to be a replacement for xControls.

We've been asking for that since about LabVIEW 6. Instead, we got xcontrols (xcontrols do a lot of what you are asking for, by the way. They are just buggy and unpredictable). NI can also have some DLL controls using a completely undocumented API. Sounds like that might be right up your street

Ah. It seems the ability came in in 2011 (was working in 2009). I was opening your controls in 2018 and back-saving to 2009, so it seems these features that are enabled are preserved with back-saving, which is useful to know. Also, I didn't realise that we now have a way (via ini-file) of making these controls multiple glyphs-I missed that memo (your link). So thanks again.

Perfect. Thanks hooovahh. Did you use flarns tool?

Almost. The classic one cannot change the colour of the scroll bars. I think I need a modern one (which can be changed).

Does anyone know of a version of this control that can have a transparent background?

This is serendipitous post. Short answer. Yes (but I'll caveat that). I have been thinking a lot about these things recently (see the installer thread) .... and I mean implementation wise. My concentration has been on the installation but it is so intertwined with packaging so I have had to think about that too. Go and put you wish-list over in the Intaller thread.

That makes a lot of sense. thanks. I'll add that to the long, long list of why I ban ActiveX and .NET from my projects.

Right. So that means the root loop is per executable instance? Or shared (via some IPC mechanism)? Because I am asking in terms of the LV task scheduler.

Indeed. In the vanilla unzip.c; (minizip 1.2) the CRC is only used for the password so that files can be extacted. I had to calculate the CRC myself during extraction for integrity.

If the DVM and power supply are SCPI compliant; you only need to change the address of the command you send.

This I know to be true (for executables). However. There is only one LabVIEW run-time per platform (which has the memory manager) so how does that affect processes? Is there a root loop per process or one global root loop?

Is that being done inside the DLL functions, rather than in the LabVIEW code? I don't see any checks in the LabVIEW code. Nor do I see the CRC being passed to a DLL function.