The useful helper routines StringToJString and StrToNSStr (and other associated ones) moved between XE5 and XE6. In XE6 you can find them in the units Androidapi.Helpers and Macapi.Helpers respectively. But how to find other useful methods? I’ll tell you what I do: Use Windows Search.
You want to go to Indexing Options to set Windows Search up to be useful.
First select Modify and browse to the Source folder and add it to the list of indexed locations. I like to add the source folder as a favorite in Explorer too, to make it easier to get back there.
C:\Program Files (x86)\Embarcadero\Studio\14.0\source
Next click Advanced and go to the File Types tab and select .PAS file and any other file types you would like to have indexed, and change them to Index Properties and File Contents. It uses the plain text filter, which in my experience is good enough, and your only option (without installing a new one).
It takes a bit for the index to rebuild, but after that you can quickly search all of the XE6 source to find APIs, Helper Methods or any number of other useful code to aid in your development process. This is where that favorite to the source folder is helpful. Either search from the root of the source folder, or browse into a subfolder to only search specific source files.
There are other indexed searching utilities, and I’ve used many of them in the past. The advantage of Windows Search (probably it’s only advantage) is that it is built in and already running.
6 replies on “Where is StringToJString and StrToNSStr in XE6?”
The GExperts Grep Search is also pretty fast. Not as fast as indexing, but that often generates a lot of background CPU usage.
Indexing uses the CPU once. The Source folder only changes when I install an update, so reindexing is rare. I used to use GREP, but it is so much slower than indexing.
Powergrep serves me pretty well. I indexed the source files too.
[…] The useful helper routines StringToJString and StrToNSStr (and other associated ones) moved between XE5 and XE6. In XE6 you can find them in the units Androidapi.Helpers and Macapi.Helpers respectively. […]
Unit Androidapi.Helpers
Androidapi.Helpers is OK!