Item Text and Notes converted to lower case in columns

[David_F]

hi,

heading says it all really - when I use Item Text or Item Notes as a column in Child Items, all text is converted to lower case. I don't remember this happening in the past.

cheers

David F.

[PureMoxie]

Interesting - it may have something to do with the release of 6.2, because I just tried this and noticed that the Item Text of items created prior to April 6 are shown correctly; items created after April 6 have the Item Text column shown as all lower case. And 6.2 was released on April 6...

[kinook]

Yes, there was a change in 6.2 to support case-insensitive searching of non-ASCII text, which does require storing the indexed text as lowercase.

You can revert the change through a registry setting. See SearchNonAsciiTextNonCaseSensitive at

https://www.kinook.com/Forum/showthread.php?t=5097

[David_F]

Always good to have options! I'll apply the registry fix and will be happy with that. Thanks Kinook.

(I realise it's not often that you want to include either Text or Notes in a column, but it does occasionally have its uses).

[David_F]

Finally got round to looking at this. Downloaded reg.zip, but can't see SearchNonAsciiTextNonCaseSensitive.

[kinook]

Try that again.

[David_F]

Redownloaded, but still not seeing it. I'm looking for SearchNonAsciiTextNonCaseSensitive.reg, right? Can't see it in reg.zip.

[kinook]

I downloaded it just now from http://www.kinook.com/Download/Misc/Reg.zip

and see it

Maybe clear your browser cache and try again. Otherwise, create a DWORD registry value named SearchNonAsciiTextNonCaseSensitive at

HKEY_CURRENT_USER\Software\Kinook Software\Ultra Recall\Options

and set its value to 0.

[David_F]

Thanks Kinook, couldn't see it for looking.

[David_F]

Returning to this issue. I recently made a view that displayed Item Notes and Item Text, and the registry fix made no difference: despite running DisableSearchNonAsciiTextNonCaseSensitive.reg, they still appeared in lower case in columns. Checked the Registry, SearchNonAsciiTextNonCaseSensitive had its value set to 0. But it had no effect on display of text.

[kinook]

I turned off that option, synced all items in the attached DB, copied some of the text to notes, and this is what I see.

[David_F]

Thanks Kinook. Had a look at the database and it was indeed as per your screenshot, with everything in Columns in the correct case. However, as soon as I made any changes to those Child items, e.g. added some text, they changed to all lower case in the Child Pane. The same if I added an item of my own. All caps got turned to lower case. I double checked the Registry, the value of SearchNonAsciiTextNonCaseSensitive is 0.

[kinook]

I added some text and it displays in the casing that I entered.

[David_F]

Again, case is preserved only until I make an edit, then everything in that item becomes lower case in the Columns view.

Could I send you the package of database plus registry export plus ini file - in case you can spot something there? It's definitely not working at this end.

[kinook]

Sure, you can post here or send to support@kinook.com

[David_F]

Had a further look at the issue. The problem is not to do with how UR transforms case, but with how you make UR display changes to an item when it's shown in the Child Items pane. I had not applied the registry fix (to restore the "old" behaviour) when I created the items, so Item Text/Notes/Title all displayed in lower case in the Child Pane. I then applied the fix, which effectively "changed" the Child Pane display. However that change would not display until a) I had made an edit to the item in question and b) had moved away from that Column view and then back again. Once I did that the Child Pane displayed case (and anything else I had changed) as it was in the Edit Pane.

I have to go through that procedure with all items created before the registry fix was applied to make them display correctly. Anything I add since then is fine.

I note that this delay in refreshing only applies to Item Text/Notes/Title. With other fields, when you change their values you see the change immediately in Child View.

Hope that makes sense... basically there's no real problem once you know what's going on, and you accept that when you have Item Text etc showing in columns, you won't see edits reflected there immediately.