Main form position

[MOL]

Hi Bogdan

Can you please set the WindowState to wsMaximized or the form's position to poScreenCenter before compiling?

Thx
Uwe

[pb]

Why?

--peter

[BogdanH]

Hi,

I'm curious to know the reason too. On the other hand, without aparent reason, I don't "like" applications which take over the whole screen when started for the first time.

Bogdan

[pb]

Hi,

I'm curious to know the reason too. On the other hand, without aparent reason, I don't "like" applications which take over the whole screen when started for the first time.

Bogdan

I agree with that sentiment, but I'm not sure that would be the effect of the request.

I haven't tried the latest version yet, but in previous versions one shortcoming for me was that it would take a long time before anything at all was put up on the screen, even just the os window decoration.  Maybe the suggestion is trying to address that.

--peter

[BogdanH]

Hi peter,

I haven't tried the latest version yet, but in previous versions one shortcoming for me was that it would take a long time before anything at all was put up on the screen, even just the os window decoration.  Maybe the suggestion is trying to address that.

Can you be more specific, please? Because here, there's no difference between first and every next GUI start speed -it is almost instant. If there's some slowing down, then I'm quite sure, it isn't GUI related.

Bogdan

[pb]

Well, on my win xp system, it can take about a minute for startup.  However, subsequent startups (if done soon enough) take only about 7 seconds, which is typical for larger programs on this system.

I believe the reason for the variation is that some amount of directory listing is going on before anything is put on the screen.  I have a lot of disks (~12), almost all of which are spun down when not active.  If a program causes windows to stat all those disks, it has to wait for all of them to spin up.  I've observed that Explorer has this problem, even when it is not being asked to report what is on any of the disks.  Most programs do not have such long startup times on initial startup, so my inference is that some amount of directory listing is going on, maybe as a side-effect, before any graphics are put on the screen.  It's been way too long since I did any windows hacking for me to remember exactly why that should be, or whether it is avoidable.

--peter

[MOL]

I'm curious to know the reason too.

Hi Bogdan

It's expected behavior in a Windows environment that programs either start up at the screen center, at the last position saved, or maximized. But not somewhere near the upper left corner of the screen as ExifTool GUI does. It's just for convenience, because every time I run the application I first have to adjust either its size or position before I can start working.

If you don't want to go the simple way, maybe you consider offering an option to save (and load) the window position and size?

Thanks
Uwe

PS: Start up time is almost instantaneously here by the way.

[BogdanH]

Hi peter,

12 of them, huh? How did you manage to connect them all? Anyway, as you suspect, many things are going on in OS's backround, so finding out settings for such system can be essential.
As you can assume from it's file size, GUI is very light application and is very economic with resources. I'm sorry you can't enjoy it's usage fully.

Bogdan

[BogdanH]

Hi Uwe,

If you don't want to go the simple way, maybe you consider offering an option to save (and load) the window position and size?

But, position/size (and everything else) is automatically saved everytime you exit GUI and automatically applied when GUI is started next time.
The only case when that doesn't happen is, if GUI is running of read only media (i.e. CD) -because setting can't be saved (user get's message in such case).

Bogdan

[MOL]

But, position/size (and everything else) is automatically saved everytime you exit GUI and automatically applied when GUI is started next time.

I'm afraid that's not the case, Bogdan.

Start ExifTool GUI (latest version)
Maximize the window
Close program
Restart application

--> Program is reset to default size and position


Uwe


EDIT:
Just checked the ini file. Width and height are not saved when closing the program after it had been maximized. The default values are used instead.

[pb]

For me, (still using 5.09), GUI remembers the last position and size of windows, EXCEPT if I close it while maximized, in which case when I next start it, it reverts to the last position and size when it was either previously closed unmaximized or last unmaximized  (not sure which).  So, it appears it needs to remember that it was maximized.

As to how I connect 12 disks...  Well, 5 are USB disks, the other 7 are internal either IDE or SATA, using expansion cards.

--peter

Correction:  I was exaggerating;  I only have 11 disks connected at the moment.  I forgot that I replaced a couple with a larger one.

[BogdanH]

Hi Uwe,

Touché -I should checked before answering. I mean, this was addressed in v4.xx, but as it seems (obviously!), I somehow forgot to implement that in v5.
Thank you fo noticing me -it's already on my to-do list.

Bogdan

[MOL]

Great, thank you Bogdan.

[BogdanH]

I knew there was something... just set GUI shortcut properties to Run: Maximized 

Bogdan

[MOL]

Hi Bogdan,

are you sure that is the proper way to handle this? I've never seen a Windows program where I had to change something hidden in a shortcut property to make it start up maximized. Besides: I didn't have a shortcut of ExifTool GUI on my desktop, so I had to look around first before I finally found what you were talking about.

I can live with this, but I would still prefer a different solution for your users.

Uwe