bug at startup fdm 545f33

[alter4]

when Options->General setting->Start minimized is unchecked the fdm start in background, main window do not show
FDM 2.1 windows xp sp2

[Alex]

Will be fixed in the next version.

[Shabba]

This bug is still alive.

version 2.5 build 715

[antini]

Have you tried build 718?

[Shabba]

Now I just ed and installed build 718. I will report if the bug has disappeared.

[Alex]

when Options->General setting->Start minimized is unchecked the fdm start in background, main window do not show
FDM 2.1 windows xp sp2

This is not bug.
Using this option allows to start FDM minimized always.
When this options is disabled FDM restores its previous state.

[Shabba]

Hi Alex, then I have a question: My desire is that FDM starts with windows and is always minimized in the system bar next to the clock. So I have set the following options:

[X] Load on startup
[X] Start minimized
[X] Minimize to tray
[X] Close button minimizes window
[X] Modify Internet Explorer's network identification

With this settings FDM starts SOMETIMES minimized in the task bar. Then I have to maximize and minimize the window again to place FDM in the system bar. That isn't correct, is it? If this is not a bug, then it is strange why this happens only sporadically.

[GDHM]

Hi Alex, then I have a question: My desire is that FDM starts with windows and is always minimized in the system bar next to the clock. So I have set the following options:

[X] Load on startup
[X] Start minimized
[X] Minimize to tray
[X] Close button minimizes window
[X] Modify Internet Explorer's network identification

With this settings FDM starts SOMETIMES minimized in the task bar. Then I have to maximize and minimize the window again to place FDM in the system bar. That isn't correct, is it? If this is not a bug, then it is strange why this happens only sporadically.

Regretfully what is stranger IMHOis that many have reported this issue (including me) and yet the threads cease without response from the FDM Team (as far as I have found).

Even if there is no known solution yet, it would be nice for this to be stated and team acknowledgemnt that the issue is recognized and what (if anything) is proposed to try and resolve.

It is a shame such a minor bug (but annoying) causes such a great application to perform imperfectly. Regretfully this bug is very noticable to the large numbers of people that experience it.