Editor for Baan (SCITE)

[mark_h]

In your developers setup put this in the Editor Read-Only Command:

c:\wscite\scite.exe -read.only $*

Then when you view a file it will open with read-only set. Then you can not type in the file. At least that is how it is working for me. Just another option besides having two versions of scite.

When I get a chance I will try to condense this thread.

Mark

[steveauckly]

I tried and can still type in the file. Did you also have to set something up in the scite properties somewhere?

[mark_h]

I did set read.only=0 in the global properties file. That is the only other change that I made - did not think that would effect it, but will check it tomorrow. I know while testing I had to close down and re-open maintain scripts in order to test the change. It looks like when you maintain a session and click on maintain scripts it reads in the developers parameters. I will also try it on one of the other developers machines tomorrow.

Mark

[mark_h]

Made the change I described(in attached jpg on previous post) on three other developers logons. All work without any additional changes to any other files.

Mark

[~Vamsi]

Mark,

Perhaps this is something to do with the version number of Scite. What version are you using?

[mark_h]

I was using 1.46 and now I am using the new 1.62 version. It works for both of these versions for me.

Mark

[steveauckly]

My problem was the version. I was on 1.39, now 1.62 works. Thanks Mark and Vamsi!!!

[Francesco]

Lately I've been getting a 'Statement not reached' warning whenever I compile scite edited code.
I'm assuming that somewhere out there is a file with a line it should not have, but instead of sweating it I thought I'd pop the question to the scite-gurus.

Also, I would like to have line numbering turned on every time I open a Baan document. I checked the API and it already had a statement in there that (supposedly) turns line numbers on.

Also, How do I define a new style and then add keywords to it?
I want all my API-stuff to show up ummm...PINK (I'm man enough to write pink code).

But mostly, I just want that annoying warning to go away. Shoo!

[Francesco]

The warning disappeared as mysteriously as it came right after I posted the above.

Ty-pi-cal

[~Vamsi]

Francesco,

Some versions of Baan would cause that statement if the last line in the program did not have a carriage return.

Baan's fix was to add a carriage return to the program every time you saved it. You can see the result of this in many scripts shipped with Baan, where there are a bunch of empty lines at the bottom of the script.

Perform a test and let us know the results.

[Francesco]

But you are right, this is probably not a scite issue. I made some changes to a script in vi and the warning persists.

(this line intentionally left blank)

[vineetu1]

Did any one face the need of viewing the same file in two seperate windows while working on a big file ?

Is it possible in SciTE Editor ? To view the same file in two windows. I need to see different parts of files while working on the bottom of the file !!

[mark_h]

A couple of thoughts - just open the file twice. You can do a save as on your local drive. Then reopen the script in Baan. Next just open up scite and open the save as file on the client.

You could also open the script in Baan, copy all lines, open new file(cntrl-n), paste the lines. Then flip back and forth.

Neither option is too clean, but should get you what you want.

[LeoSpett]

i installed the scite editor and some functionality doesn´t work correctly. i am using windows 2000.

for example if some word appears in the source and i want to use it again the autocomplete doesn´t appear.

the help (f1) doesn´t work and the arguments for the function doesn´t appear too.

sory for my english and wait for help

[mark_h]

Make sure these are in either local user options or scite user properties file:

autocompleteword.automatic=1
command.help.$(file.patterns.baan)=$(CurrentWord)!D:\BaanHelp\tt2.hlp

You must have the tt2.hlp command on the client PC in order for it to work. You just point this command to your help file.