Large Project Multi Selection Bug

Well, now I started using the multi selection feature. I found at least one bug.

First, I was using "Shift" to select a wide range of text with a single mouse click. But what I didn't know, was that the multi selection feature is restricted to one file at a time. So selecting alle strings from two files, will only perferm the desired action (Could be SPACE/Select for translation). Well this might not be a bug - but it's not intuitive ;-)

Secondly, we got a lot of files where blank texts gets "translated" (bound fields where headertext is ""/empty string). So I select all strings in the file holding shift clicking first and last string. Now i hold "Ctrl" and click the strings I want to remove from the selection. But as I click on a string a "deselect" it (removing the blue bagground) it gets highlighted (in a wide selection there is "always" one item thats highlighted/selected above the others - this is the last field you have "touched"). So the bagground-highlighting seems to be working, but if the last item I have click was a "deselect", this will actually be the only item the desired action would be applied to (instead of being the only one not to apply the action on e.g.). This would be a bug for sure..

And last but not least, I all into semantic as well.. Selecting a wide range of strings, I would expect the first string to have the lowest number and the last to have the highest number. We havn't yet gone to the translation part, but I fear my translator will translate "Terms and Conditions" from bottom to top - making it hard for the translator to have a nice flow in the text. But you might got this covered by sorting by how the texts is ordered in the document. Not sure this is a bug - but i fear how this will work out..

Thank you for an overall great tool ... Very powerfull when you learn how to use it :-) Will keep posting my observation :-)

"CTRL" + "SPACE" = Disable Document
"SHIFT" + "SPACE" = Hide Selected Strings

Personally I think they are too close to each other - Hitting disable document is a little annoying - but i know I just have to think and concentrate more ;-)

Germany

> "CTRL" + "SPACE" = Disable Document
> "SHIFT" + "SPACE" = Hide Selected Strings
>
> Personally I think they are too close to each other - Hitting disable document is a little annoying - but i know I just have to think and concentrate more ;-)

Hi Nick,

I have changed the shortcut to disable the complete file to CTRL-SHIFT-SPACE, which should be harder to hit by accident. This is in version 4.7x.0096.

I have also added some text to the tooltips (and the context menu) to describe the keyboard shortcuts.

Phil

Again - thank you!! smile

A little correction:

First, I was using "Shift" to select a wide range of text with a single mouse click. But what I didn't know, was that the multi selection feature is restricted to one file at a time. So selecting alle strings from two files, will only perferm the desired action (Could be SPACE/Select for translation) on one file. Well this might not be a bug - but it's not intuitive ;-)

Germany

Hi Nick,

Selecting the strings from two files ought to work. It's working for me, at least with the most recent version.

I can reproduce the effect with the StringIDs in the reverse order. In the latest version (4.7x.0093), which I have just uploaded, the selected items are sorted first. This should fix the problem.

Phil


Germany

Hi Nick,

I have just been looking into the problem with empty strings.

I have found an effect which surprised me. There are two ways of viewing the strings in an ASP page (on in controls on a Windows Form):

  • in a structured list or
  • in a flat list

You can switch between these options in the drop down +- menu (with an icon showing + and - buttons).

In the flat list, the empty strings are not displayed. In the structured list, they are displayed.

From this, I surmise that you are using the structured list. In order not to see these empty strings, I recommend switching to the flat list.

However, I have decided to end the stupid problems caused by empty strings and simply ignore them all. I will have to check for them in quite a few places, so it is not entirely trivial, but I will make this change very soon. There are really no good reasons to translate empty strings, so it makes little sense to show them!

Phil

Germany

In version 4.7x.0094, empty strings should not be displayed at all.

Phil


Thank you for adressing our issues (as always)! Really good service!

Looking forward to use the new version with the fixes :-)

Hope you removed empty strings from export as well ;-)