Undefined BOOTPATH when importing .reg-files

[deploy]

This was easy enough to fix in my end, just thought you might want to have a look at this. Maybe it is intended to work this way, maybe it is something for the fixes list.

I am working with a IA setup created from template Basic Setup (lastest version of IA).
When importing a .reg-file (exported from regedit) I find that entries like:
"Command1"="C:\\somefolder\\someprogram.exe"
fore some reason are translated to:
Value: Command1
Data: $BOOTPATH$\somefolder\someprogram.exe

Boothpath is not listed in the help file and not defined in my project. After some searching in the forum I found MYBOOTPATH (files -> special folders).

If IA converts C:\\ during import of a .reg file, shouldn't it use MYBOOTPATH and not BOOTPATH?
If IA converts C:\\ during import of a .reg file, shouldn't IA define MYBOOTPATH under setup globals?
Or at least define BOOTPATH?

Regards

[FrancescoT]

Dear User,

I suppose it is by design and you have to define the variable as you need.

Regards