A strange application behaviour on Windows 10 Creators Edition (1703 build)

I found a solution to my issue. I don’t fully understand why this has fixed it. I would like to share my findings.

My multi-dll application has 20+ DLL and 1 exe application.

Previously
The First Procedure in my Exe application used to be source procedure called (StartupSequence)

After lot of trial and error, I’ve changed the First Procedure to a window procedure called LauncherProc:

Added the following code in LauncherPro (OPENWINDOW )
0{PROP:HIDE} = TRUE
StartupSequene()
POST(EVENT:CLOSEWINDOW)

This seem to have fixed the issue. I don’t know why!!! I have done some serious amount of testing and it seem to be working fine.

Cheers

1 Like