Tough words about GUI

[admin]

Should be fixed in next version.

It isn't Moused-over tab still does not fill completely.

tab_fill.png

Re: drawing glitch with gaps, I still get the active tab overlapping an edge of its left neighbour while exposing a 1 pix gap to its right neighbour

Since it works well now in XP and Win7, there must be a problem with your skin/theme. Looks like I cannot support both the standard themes and your theme at the same time.

[zer0]

Since it works well now in XP and Win7, there must be a problem with your skin/theme. Looks like I cannot support both the standard themes and your theme at the same time.

Sure, it could be a problem with the visual style. That said, XYplorer isn't very "skinnable", but maybe that's something that can be touched upon as part of "Support for Win 7 stuff" that's on the roadmap

[zer0]

A few betas ago, we have received (thank you for it )

Code: Select all

v9.11.0011 - 2010-05-26 16:06
    * Installer: Now you face the prompt "Please close any running
      XYplorer instance before you continue." if any XY instance is
      running.

As it currently stands, there is no enforcement of that check, i.e. one can click "OK" even though one hasn't actually closed an instance of XYplorer. It may/may not be a well-known fact that the default answer to every dialogue box is "Cancel". With that in mind, I believe that this instance check should be made more persistent. IOW, installer should make sure that XYplorer is actually closed before proceeding with installation.

Its current role is weak -- it's a notification rather than a warning. And it should be a warning: it involves risk and it is immediately relevant and actionable. Such strict checks are not unprecedented and are a good way to instil such "discipline" for those who use an installer version.

[admin]

A few betas ago, we have received (thank you for it )

Code: Select all

v9.11.0011 - 2010-05-26 16:06
    * Installer: Now you face the prompt "Please close any running
      XYplorer instance before you continue." if any XY instance is
      running.

As it currently stands, there is no enforcement of that check, i.e. one can click "OK" even though one hasn't actually closed an instance of XYplorer. It may/may not be a well-known fact that the default answer to every dialogue box is "Cancel". With that in mind, I believe that this instance check should be made more persistent. IOW, installer should make sure that XYplorer is actually closed before proceeding with installation.

Its current role is weak -- it's a notification rather than a warning. And it should be a warning: it involves risk and it is immediately relevant and actionable. Such strict checks are not unprecedented and are a good way to instil such "discipline" for those who use an installer version.

What risk?

And what do you mean by "the default answer to every dialogue box is "Cancel"."?

[RalphM]

I'm with Don here.
The only risk is, that you get an error message later on, because XYplorer.exe couldn't be replaced because it was still running.
In the short timespan needed for the install, one should still remember the message that was apparently ignored before.
And as a result you're still stuck with the previous release, which isn't too dangerous me thinks.

[PeterH]

A few betas ago, we have received (thank you for it )

Code: Select all

v9.11.0011 - 2010-05-26 16:06
    * Installer: Now you face the prompt "Please close any running
      XYplorer instance before you continue." if any XY instance is
      running.

As it currently stands, there is no enforcement of that check, i.e. one can click "OK" even though one hasn't actually closed an instance of XYplorer. It may/may not be a well-known fact that the default answer to every dialogue box is "Cancel". With that in mind, I believe that this instance check should be made more persistent. IOW, installer should make sure that XYplorer is actually closed before proceeding with installation.

Its current role is weak -- it's a notification rather than a warning. And it should be a warning: it involves risk and it is immediately relevant and actionable. Such strict checks are not unprecedented and are a good way to instil such "discipline" for those who use an installer version.

What risk?

And what do you mean by "the default answer to every dialogue box is "Cancel"."?

Maybe see it the other way?

As you already seem to check for active XY, you could also do it *after* the dialogbox. And ask for termination again, if XY still active.
And if user doesn't want to terminate, he needs a "Cancel" - canceling installation.

[admin]

A few betas ago, we have received (thank you for it )

Code: Select all

v9.11.0011 - 2010-05-26 16:06
    * Installer: Now you face the prompt "Please close any running
      XYplorer instance before you continue." if any XY instance is
      running.

As it currently stands, there is no enforcement of that check, i.e. one can click "OK" even though one hasn't actually closed an instance of XYplorer. It may/may not be a well-known fact that the default answer to every dialogue box is "Cancel". With that in mind, I believe that this instance check should be made more persistent. IOW, installer should make sure that XYplorer is actually closed before proceeding with installation.

Its current role is weak -- it's a notification rather than a warning. And it should be a warning: it involves risk and it is immediately relevant and actionable. Such strict checks are not unprecedented and are a good way to instil such "discipline" for those who use an installer version.

What risk?

And what do you mean by "the default answer to every dialogue box is "Cancel"."?

Maybe see it the other way?

As you already seem to check for active XY, you could also do it *after* the dialogbox. And ask for termination again, if XY still active.
And if user doesn't want to terminate, he needs a "Cancel" - canceling installation.

I cannot check whether the XY instance is running that is about to be installed. I just can check whether any XY could be running. I think it's good as it is.

[zer0]

And what do you mean by "the default answer to every dialogue box is "Cancel"."?

Read 'em and weep: http://blogs.msdn.com/b/oldnewthing/arc ... 54734.aspx

As you already seem to check for active XY, you could also do it *after* the dialogbox. And ask for termination again, if XY still active.
And if user doesn't want to terminate, he needs a "Cancel" - canceling installation.

The best place to check is immediately prior to copying of files being initiated. That way, a warning informing that an overwrite could not be performed can be bypassed altogether.

[TheQwerty]

I cannot check whether the XY instance is running that is about to be installed. I just can check whether any XY could be running. I think it's good as it is.

I suggested this in the other thread, but don't recall anyone responding. Couldn't you place the running process check after prompting the user for the destination folder? Then you'd know to only care about the xyplorer.exe process from that folder.

[admin]

And what do you mean by "the default answer to every dialogue box is "Cancel"."?

Read 'em and weep: http://blogs.msdn.com/b/oldnewthing/arc ... 54734.aspx

As you already seem to check for active XY, you could also do it *after* the dialogbox. And ask for termination again, if XY still active.
And if user doesn't want to terminate, he needs a "Cancel" - canceling installation.

The best place to check is immediately prior to copying of files being initiated. That way, a warning informing that an overwrite could not be performed can be bypassed altogether.

Ah, now I see how that "default" was meant...

@all: Once again: For technical reasons I cannot test which XY instance is running.

[zer0]

@all: Once again: For technical reasons I cannot test which XY instance is running.

But can you check if ANY instance of XYplorer is running immediately prior to copying of files and prevent the installation from proceeding unless NONE are running?

[admin]

@all: Once again: For technical reasons I cannot test which XY instance is running.

But can you check if ANY instance of XYplorer is running immediately prior to copying of files and prevent the installation from proceeding unless NONE are running?

Sorry, but I have no time to continue discussing this.

[zer0]

With "Environment Variables..." -- why an ellipsis? it's not a long title and no additional info is asked for -- added to Help menu, I trust that myself and others would welcome the following enhancements:

1. Window keeps its size to resized value within and between sessions.
2. Vertical scrollbar placeholder (outlined below) disappears when windows is resized to show all contents.

env_vars.png (102.26 KiB) Viewed 1369 times

[admin]

With "Environment Variables..." -- why an ellipsis? it's not a long title and no additional info is asked for -- added to Help menu, I trust that myself and others would welcome the following enhancements:

1. Window keeps its size to resized value within and between sessions.
2. Vertical scrollbar placeholder (outlined below) disappears when windows is resized to show all contents.

All menu items that open another window have an ellipsis.

1. Not worth the effort, the memory, the loadtime costs, the disk space.
2. Agreed, but did not find a way yet; working on it.

[zer0]

All menu items that open another window have an ellipsis.

Erm, dare I ask why? User interface guidelines -- such as http://msdn.microsoft.com/en-us/library/aa974176.aspx -- say that ellipses are to be shown "only when additional information is required" and "Don't use an ellipsis whenever an action displays another window".

2. Agreed, but did not find a way yet; working on it.

Thanks!