Moderators: Hacker, petermad, Stefan2, white
That's rightszlori wrote:The access-keys of dialogs don't depend on *.mnu files.
*.mnu files are for the menu.
That's right again. This way I meant "the english language file is built in". You can use an external language file, but if there is no language file at all TC uses that one compiled into the exe.szlori wrote: Access keys in dialogs depend on *.lng files, but for this there's no separate English one, at least I couldn't find one in my install dir.
Sheepdog wrote:That I did not know (perhaps because I use german -language and there it is "Übernehmen").white wrote:What are you talking about? The apply button normally has access key A.
But I think it would be a good idea to have a TC wide key (okay it's no access key) to apply the changes.
Quote from MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Fundamentals of Designing User Interaction > Input Basics
Also, avoid using a character usually assigned to a common function. For example, when you include an Apply button, reserve the "A" — or its localized equivalent — as the access key for that button.
Quote from MSDN Home > MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Fundamentals of Designing User Interaction > Getting Started
The Importance of a Well-Designed Interface
The usability of your application's design is not just a philosophical nicety for your consideration; it is essential to the success of your application. The investment you make in the design of your application contributes not only to supporting and keeping your existing customers, but also to expanding your customer base. Therefore, your investment in the design of your application directly affects your current and future bottom line.
Quote from MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Fundamentals of Designing User Interaction > Input Basics
Keyboard Input
The keyboard is used primarily for entering and editing textual information. However, the Windows interface also supports the use of the keyboard to navigate, toggle modes, modify input, and, as a shortcut, invoke certain operations. The fact that users can navigate through the interface by using the keyboard as well as by using the mouse is a fundamental principle and one of the key advantages of the Windows user interface.
Quote from MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Fundamentals of Designing User Interaction > Getting Started
Lack of Adequate Keyboard Support
Keyboard support provides efficiency for many users, but for those with sight impairments or repetitive-stress injuries, it is essential. Keyboard support means including keyboard access to all of your application's functions. It takes only a little time to confirm that your application's interface provides a logical tab navigation order.
Quote from MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Windows Interface Components > Secondary Windows
Title Bar Text
Because dialog boxes generally appear after the user clicks a particular menu item (including shortcut menu or cascading menu items) or a command button, define the title text for the dialog box window to be the name of the associated command. Use book title capitalization.
Quote from MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Fundamentals of Designing User Interaction > Getting Started
The Need for Improved Simplicity
Despite the popular support for Windows, there are still substantial challenges in providing the best experience for users. Computers are still too complicated to use, and support costs are high. Users frequently complain about the number of features they find in applications; they can't find the features they care about, and they can't figure out the features they do find.
Many users expect a computer to be as easy to use, and as predictable and reliable, as an appliance. They want a computer to work in a way that is familiar to them. Therefore, simplicity of design involves issues that must be addressed by everyone building applications for Windows.
Delivering simplicity does not mean just removing functions. It requires work. Even a simple interface can require a significant investment of code. However, the rewards and benefits are substantial, including reduced training and support costs and productive, loyal customers.
This is not a state, it's a repeatable operation.Bug in menu Show/Only Selected Files
Selecting this option does not change the check mark in the menu.
Yes, but many new users didn't know that MkDir should be used to create "folders".F7 NewFolder -> title "Total Commander" (Folder??? I thought you always called that directory)
Well it is listed among the 'states' is it not? I think if the check mark is not changed, this operation should be listed in a separate section of the menu.Hacker wrote:This is not a state, it's a repeatable operation.Bug in menu Show/Only Selected Files
Selecting this option does not change the check mark in the menu.
Exactly my point. See what impact simple rephrasing can have. It's a huge improvement to replace directory with folder. Don't tell me that is too much work. The benefits by far outway the trouble of replacing. The term directory has no place in the 32 bit version of Total Commander.Hacker wrote:Yes, but many new users didn't know that MkDir should be used to create "folders".F7 NewFolder -> title "Total Commander" (Folder??? I thought you always called that directory)
Honestly, these would be at the bottom of my wishes for TC.Don't you think the check mark should be temporarily changed? And don't you think the 'state' listed behind the current dir should be changed temporarily?
This would be a bit higher on my list.I wonder if it would be more useful if the 'state' (showing only selected files) or at least the current selection was more sticky. Suppose you have carefully selected certain files from a long list and executed the operation Show/Only Selected Files. Suddenly a popup window appears because you have new mail. Ouch.. you can start all over again.
What are your wishes? And to whose benefit are those wishes?Hacker wrote: Honestly, these would be at the bottom of my wishes for TC.
I already did a quick scan of my OS (Windows 98 ) and some MS programs. I found very little flaws in their user interface. Maybe you can show us the mess you are talking about?Sheepdog wrote:Just taking these guidelines and checking Windows itself or other MS programs would show you a mess too.
And they have a bunch of teams and a pile of money to make sure their programs fit these guidelines.
I think Total Commander will improve far more by improving it's user interface and documentation than by adding new features. We all would benefit from that. I am a very experienced user and think most people would call me an expert user. So I would not benefit most from improving the user interface. I have no trouble in finding ways to do whatever I want to do. So I do not want improvements mainly for my own personal needs. Do you?Sheepdog wrote: Thus I can hope that @ghisler is not struggling days and days through all dilaogs to find a missing access key but programming new features I can use with my licence from 1995.
The default command button should be the Go to file button when Search results has focus.Quote from MSDN Home > MSDN Library > Win32 and COM Development > User Interface > Official Guidelines for User Interface Developers and Designers > Windows Interface Components > Secondary Windows
Pressing ENTER should always navigate to the default command button, if one exists, and invokes the action associated with that button. If there is no current default command button, then the ENTER key can be used for a control.
Yes, that is a known bug.Open Custom Columns configuration, doubleclick on any available column, close the appeared dialogue, and move a mouse. The mouse starts to move behind itself the allocated column (though mouse buttons is not pressed).
