Treeview control reverts all icons from imglist back to default 0 index icon

[davidc]

The issue is probably caused by the fact that you add in the controls dynamically. The grid will anchor relative to the size parent control at time of insertion. In this case, the grid has a set size, but they parent panel’s size may vary depending if the user resizes it.

Why don't you include these controls in the designer? You can always set control's Visible property to False if you need to hide it.

[MDinice]

It seems the .NET serializer for the TreeNodes does not save the ImageIndex. We are looking at finding an alternative solution.

The ImageList issue also has do with the .NET serialization process.

Any updates on the following project saving, closing, and reopening issues:
ImageList / Treeview icons all switching back to the default 0 index icon (I'm holding off on changing them back because there's so many of them)?
Splitter Control resetting to 4 after switching it to 2

[davidc]

We made changes to the way we save that information to the psf file that preserves the ImageIndex information and the image key names. Once it clears the QA process, we will release the build.

Nothing yet on the splitter control.

[davidc]

Good news. The changes we made also fixed the splitter issue.

[MDinice]

We are investigating this issue and will post as soon as we have any updates.

One other thing I just noticed with the Treeview. I removed the splitter panels for now and am using a Treeview and 2 Panel controls to give it the 3 panel splitter look.
In designview the Treeview border style looks Fixed 3D

trvwDesigner.PNG (17.65 KiB) Viewed 2985 times

At Runtime and after an exe build it actually looks Fixed Single

trvwRunTimeandEXEBuild.PNG (17 KiB) Viewed 2985 times

Its really noticeable if you look at the bottom edge of the control

[davidc]

The designer may vary slightly from the final script output. Different hosts and OSes may produce slightly different results. For example, High DPI support is dependent on the running executable.

This is one of the reasons we have the Preview command. It allows you to see what the final GUI looks like in action.

David

[davidc]

We just released a PowerShell Studio service build (v5.5.149). It should resolve the issues you posted.