2015 Fast File format disrupts Window-Run-Time Position

[Darren]

---

@reddog wrote:

A quick update on this issue based on my experiments. The bug has been closed as fixed in LV 2023. With LV 2023 installed, fast file format enabled, and the source file settings for the startup VI modified in the build spec so that the window run-time position is minimized, I no longer see a flicker when the exe starts. However, if I disable fast file format, the flicker is visible again.

---

Are you saying that your experiment shows a new bug? i.e. that the buggy behavior now happens with FFF disabled instead of enabled?

[Cepera]

Reposting my 8/8/2023 response to a similar thread :

I have revisited this feature in LV 2023 Q3 64-bit. The problem with the flashing window seems to be gone. I tested a couple of builds with FFF enabled on two machines: one with Core i7 CPU and M2 SSD and one with Core i3 CPU and mSATA SSD.

With all that said, I find this feature to be of minimal value: while executables that use this feature are about 30% smaller than without it, the load time is pretty much the same.

[reddog]

---

@Darren wrote:

---

@reddog wrote:

A quick update on this issue based on my experiments. The bug has been closed as fixed in LV 2023. With LV 2023 installed, fast file format enabled, and the source file settings for the startup VI modified in the build spec so that the window run-time position is minimized, I no longer see a flicker when the exe starts. However, if I disable fast file format, the flicker is visible again.

---

Are you saying that your experiment shows a new bug? i.e. that the buggy behavior now happens with FFF disabled instead of enabled?

---

I came upon this thread since it was linked from this thread about the startup VI window flickering into view upon startup of a built application. This is the problem I care about solving since the exe I'm building is intended to be a background service and not something that will have any UI presence. In my case, I am using grpc-labview to build a gRPC service. Attempts to resolve the issue seem to have a lot of mixed results where some users report certain work arounds work for them while others report they have no effect. I am in the camp where none of the previously reported work arounds to eliminate the window flickering into view have worked for me. What I described earlier with FFF has been the only combination of things I've found so far that has eliminated the flickering.

I don't think the change introduced a new bug. If I disable the 2023 RTE and revert to an older version of the RTE I have installed, I see the same flickering regardless of whether or not FFF is enabled. So it seems more likely to me that the bug was present in multiple code paths and only one of them got fixed.

[wiebe@CARYA]

---

@reddog wrote:

I don't think the change introduced a new bug. If I disable the 2023 RTE and revert to an older version of the RTE I have installed, I see the same flickering regardless of whether or not FFF is enabled. So it seems more likely to me that the bug was present in multiple code paths and only one of them got fixed.

---

I hope these kind of things finally get some priority.

I wouldn't be surprised if this is discarded to the bottom of the bug list as a 'cosmetic' issue. Assuming there hasn't been someone working on a fix for 7 years (if so, may put a team on it).

This bug stops my executables from having a splash screen, although the users complain about not seeing results for 10 seconds when starting. But, it's either a splash and 40 MBi or no splash and 20 MBi.

In fact, these kind of bugs make a LabVIEW programmers life very difficult. One or two tiny requirements (e.g. splash screen, smaller executables), estimated 2-4 hours now turn into days of testing, trying, posting, etc.. The end result is pick one: splash or small(er) exe.

Seemingly insignificant bugs\idiocrasies can have a huge impact.

Please prioritize.