Talk:ProjectItem

Thoughts on combining Pages

This page is similar to the pages:

• ProjectItem class
• ProjectItem class/Type String property
• ProjectItem class/Get All Descendents method

What are some ideas on the best way to combine this information? Because it should be accessible from the pages listed above (as well as others), I suggest this page is renamed to "Type String" and linked to from the other pages. --Q (talk) 04:53, 9 May 2020 (UTC)

I think the first part should go into ProjectItem class and ProjectItem class/Get All Descendents method, respectively. The table belongs to both ProjectItem class/Type String property and ProjectItem class/Get All Descendents method. I don't think it should be copied under both. Instead, maybe put it under one of them and link from the other. I assume this is what the LabVIEW help does as well. --Logmanoriginal (talk) 18:23, 9 May 2020 (UTC)

I'm starting to re-think this decision now that I am seeing almost the exact same table in the Project Explorer page too. Maybe there needs to be a ProjectItem page with the Type String and Type GUID table that the rest refers/links to. --Q (talk) 17:46, 7 June 2020 (UTC)

This is probably the best compromise, especially considering that the table can be used for other purposes as well (i.e. manually editing type data). --Logmanoriginal (talk) 20:00, 7 June 2020 (UTC)

.ctl (presumably .ctt) give {64A9BF48-4C55-45DB-8F18-9C796DA0C113} for me in LabVIEW 2020 64 bit.

.ctl (presumably .ctt) give {64A9BF48-4C55-45DB-8F18-9C796DA0C113} for me in LabVIEW 2020 64 bit.--Wiebe CARYA (talk) 14:39, 9 July 2021 (UTC)

Both LV2019SP1 (32-bit) and LV2021b10 (32-bit) return {64A9BF48-4C55-45DB-8F18-9C796DA0C113} for class private data and {D60740D6-F254-4BBC-5675-8858F35B810E} for .ctl, .ctt, .vi, etc. as listed on this page. Can you confirm that this is not a private data control? --Logmanoriginal (talk) 19:11, 10 July 2021 (UTC)

Ah, :palmface: Yes, those are class private data ctls.