1. Describe your environment: What is your industry? What is your role in your organization? Describe your stakeholders.
I am a structural engineer of 20 years working in the bridge and heavy construction field. I create designs for platforms, shoring towers, lifting devices, formwork, crane foundations, etc. Pretty much anything the field needs to do complex structural work. My design calculations need to be simple and easy to follow by other engineers but I do not need to take months to get them to a level of pristine publishable quality. Although I create drawings that regular field crews must be able to understand for their own safety, calculations only get circulated amongst other engineers and on rare occasions to non-technical managers and staff.
2. What version of Mathcad are you currently running?
3. Describe the problem you are trying to solve. Please include detailed documentation such as screenshots, images or video.
I just got into programming and I am enjoying the brevity of Mathcad programming for engineering concepts as opposed to VBA programming in Excel.
However, I find that "home" and "end" keys do not operate the same as what I would normally expect. When editing a program, the keys take you to the beginning/end of the region, not the front or end of the current line of code. While in 'text regions' the home/end keys work as one would expect. Even the "Ctrl-Home/Ctrl-End" will at least get you to the front and end of the region but in a 'math region' it takes you to the beginning/end of the document.
Basically, the home/end key behavior is not consistent in the same app and different from 99% of all other apps.
I believe the problem here is that Mathcad treats 'math regions' as different from 'text regions' in that it treats it as single line entities. But you also market 'programming' so there needs to be more consistent home/end behavior, especially when the programs are hundreds or even dozens of lines long.
Suggestion: Home/end should be looking for the next hard return, soft return and/or region boundaries in any region. And Ctrl-home/end should get you to the beginning/end of the current region, then pressing it again at the beginning/end of a region could then take you to the beginning/end of the entire document.
Suggestion: The Ctrl-Up/Dn keys should also act consistently. Right now Ctrl-Up will skip from region to region but will jump up to the header objects before scrolling up to previous regions in the main body of the document--not appropriate (I'm not so indecisive that I am frequently changing my titles). The Ctrl-Dn key does nothing. Ctrl-Up and Ctrl-Dn should be consistent in jumping up and down the the next text or math regions in sequence.
In general, it is important to have consistent navigation throughout the app, and it is not wrong if these actions are similar to other competing apps. We all use the same keyboard layouts so it's natural to expect the same between apps.
4. What is the use case for your organization?
Obviously everyone in my company would benefit from consistent navigation in a document. Less lost time and getting frustrated with an app that behaves differently than most other common apps.
5. What business value would your suggestion represent for your organization?
Not a huge value. We are not going to loose work over this inconsistency and it's amazing how people will adapt to their circumstances. I'm sure that all Mathcad users across the world would find a slight value each, and this would give a better 'polished' feel to Prime.