Ranorex Forum

Ranorex 5.3.0
Windows 7

This worked in 5.2.2 and previous, so the bug was introduced in 5.3.0.

When typing the name of a new file that is being added to the project, hitting the space-bar makes the cursor move back to home in the text box instead of adding a space.

Previously hitting space would add a space and then convert that space to an underscore "_" upon clicking "Create".

To reproduce:
1. Add a new file to the project.
2. In the "New File" dialog enter a file name that contains a space such as "New File". Upon hitting space, the cursor jumps to the start of the text box.

Let me add that it does this only when the cursor is at the end of the name. If the cursor is in the middle of a word it will add a space.

Also, when the cursor is at home, the space bar will move the cursor to just after the first letter, but will NOT add a space.

Hi krstcs,

Thank you for reporting this issue , I already forwarded it.

Regards,
Markus

Any update on this? It's still not fixed in 5.3.2.

This is one of those little bugs that is rather annoying, even if it isn't a critical functional issue.

Hi Kelly,

I am afraid you are right, since this bug fix will be released as part of a bigger release of related issues/features.
I cannot give you a guarantee but it should be released with Ranorex 5.4.
Thank you for your patience.

Regards,
Markus

Thanks Markus!

I guess some kind of fix was deployed into 5.4.0 for this but it is still not as it was before. When naming new file user cannot use space(bar) at the end of the string - it doesn't jump to the start, but it also doesn't do anything.

Hi Primoz,

We fixed this in the way that it is no longer allowed to add spaces at the beginning and the end of a new file but in the middle. The spaces in between will then be converted to underlines.

Regards,
Markus

Markus,

This is not how it used to work before you guys broke it in 5.3. It used to allow us to hit space bar at any point (start, middle, end) and would turn that into an underscore.

If you aren't going to allow us to use spaces in file names (which is fine since .NET doesn't allow them in construct names) then you should just convert all space bar hits directly into underscores in file names, test case, etc., regardless of whether it is at the beginning, middle, or end of the name.

In other words, if the cursor is in one of the designated name/rename boxes where spaces aren't allowed, then hitting the spacebar should type an underscore instead, just as if I hit the underscore key. There should be no post-typing conversion.

UX-wise, it is bad design to enforce changes like this AFTER the user has submitted the data. You should always convert the format upon entry, not upon save, so the user can see immediately what the final name will look like.

Hi Markus,

I must agree with krstcs about this. Current behavior is not very user friendly. I'm not using spaces in names, but it was very handy using the space bar knowing that all spaces will be then converted to underscore. With current changed workflow, the space bar is practically useless for naming. If it can be used only in the middle of name string, it's faster to use the underscore key instead The original workflow was just handy behavior.

Hi Kelly und Pavel,

Thank you for your valuable responses, this is very much appreciated.
And I already forwarded them.

Regards,
Markus