Hi,
I have a client machine which has Windows 7 and working on Baan ERP LN FP7 package. I did install Scite editor and made necessary changes to the properties file and it opens up, but the Baan language and data from Baan api file are not considered and hence not highlighted.
When I in the editor and when I try to comment a set of lines, also it gives an error message "Block comment variable 'comment.block.' is not defined in SciTE*.properties!"
Can someone help me on the above issues.
Thanks.

(1) Do you have the baan.properties file in the scite directory?
(2) Is your sciteglobal.properties file correct? Baan is specified in several spots.

Under options you should see baan.properties. This file needs to be in the install directory and then the sciteglobal.properties file should include some baan options. You should be able to get both of these files from the code and utilities forum.

Also keep in mind - if you use scite.properties or sciteuser.properties they will go into a different directory. On my win 7 desktop they point to c:\users\username - username is how I log into the desktop. We do not use these two files everything goes into the sciteglobal.properties file - we have scite installed on network drive. This way we can go to any desktop and edit code.

Hi Mark,

I have the file baan.properties and sciteglobal.properties in the scite directory. However, when I open the script it open scite editor, but in Options I do not find baan.properties listed. Can you please help me further on this issue.

Have you tried down loading just the sciteglobal properties file from code and utilities forum? When I get to work on Monday I can attach it to the thread. Not sure how quick you need this.

Just curious: Why not using the Eclipse based LN Application Studio if you work on LN FP7? You will get features like syntax highlighting, code completion, open declaration, etc. out of the box.

Uploaded a copy of our sciteglobal properties file. Put it in a .txt extension. I also removed our server name for security. You can search for baan in the file to see what all is included.

I have a related query on the same topic.thats why i didnt create a new one.

I cant box comment in my scite, The Error comes as
"
Box Comment Variables 'comment.box.start' 'comment.box.middle' and 'comment.box.end' are not defined in Scite *.properties.
"


Although i downloaded and save all the three files in my c:/Wscite Directory
(The files are SciTEGlobal.properties,baan.api,baan.properties)

The Editor also doesnt show Open Baan.properties in the Options Window.

Somehow the Scite doesnt seem to have read the Baan files.

What i am missing?

Look at the sciteglobal.txt file I attached in a post above. Make sure you scite global properties has the import baan under the import all language specific properties files.

If you put the .txt (really sciteglobal.properties) I attached above in c:\wscite you might have to edit to point to the correct api files. The way to check if you are opening the right file is to use options open global options file. Search for baan and make sure everything looks okay. Don't for get toward the bottom it should have import baan.

Once you see baan in the options you should be able to now open the baan properties file. Then you can search on the comment.block.baan , comment.box.start.baan, comment.box.end.baan, or comment.box.middle.baan - make sure they are |'s. Or you can just set the variables.

Look at the sciteglobal.txt file I attached in a post above. Make sure you scite global properties has the import baan under the import all language specific properties files.

If you put the .txt (really sciteglobal.properties) I attached above in c:\wscite you might have to edit to point to the correct api files. The way to check if you are opening the right file is to use options open global options file. Search for baan and make sure everything looks okay. Don't for get toward the bottom it should have import baan.

Once you see baan in the options you should be able to now open the baan properties file. Then you can search on the comment.block.baan , comment.box.start.baan, comment.box.end.baan, or comment.box.middle.baan - make sure they are |'s. Or you can just set the variables.

Thanks a Ton.It worked.

Had a question in my Mind. I saw in SciteGlobal.properties file, they just had an import all * statement and this is supposed to be the latest version whereas your file had all the import languages specifically and your post seems to be few years old.

Why doesnt Scite have that in latest version?

I can't answer that - since we lost admin rights to our desktops I really have not tried to update scite or even keep up with the changes.

I can't answer that - since we lost admin rights to our desktops I really have not tried to update scite or even keep up with the changes.

Admin rights not required for scite. scite was installed into %TEMP%\scite folder, where there is always write permission. Then
Control Panel-->All Control Panel Items-->User Accounts-->Change my environment variable and added %TEMP%\scite to the PATH variable. Using this method without admin rights, for quite sometime...

Thanks a Ton.It worked.

Had a question in my Mind. I saw in SciteGlobal.properties file, they just had an import all * statement and this is supposed to be the latest version whereas your file had all the import languages specifically and your post seems to be few years old.

Why doesnt Scite have that in latest version?

Scite added imports.include/imports.exclude and "import *" since version 2.29. currently it is 3.3.6. Around 2.29, scite no longer loaded baan as default, as it was added imports.exlude list in the downloaded global properties file. Explicit declarations worked through out.

Admin rights not required for scite. scite was installed into %TEMP%\scite folder, where there is always write permission. Then
Control Panel-->All Control Panel Items-->User Accounts-->Change my environment variable and added %TEMP%\scite to the PATH variable. Using this method without admin rights, for quite sometime...
Did not try to install to the temp directory - but any install I try now requires an admin account and password on our machines. I can't change environment variables.