Hi,
I tried to compare both sources and found that the differences are quite
extensive. Trying to add all codes with direct reference to OnKey and
recompiling scite, there appeared no compiling error. But using the exe
thus obtained (yes, I'm under windows now) and testing the snippets, I
got error messages in UpdateStatusBar or something. Looking back into
the SciTE-tools svn, I realized that there are more codes defining
UpdateStatusBar and other necessary procedures. So I'm afraid that
merging all these into the official scite source might yield exactly the
same source as the SciTE-tools svn.
You may remove any references to scite.UpdateStatusBar in the scripts. I
have it there to show the current key sequence to the user. I believe
you only have to modify Extender.h, The *Extension.cxx files, and
SciTEWin.cxx for windows (SciTEGTK.cxx for linux) to get OnKey working.
That being said, I turned to look into the properties files to find what
makes the font/color differences. It turned out that the following lines
in lua.properties for SciTE-tools somehow overrides my language specific
settings:
You can substitue your lua style settings for the ones in SciTE-tools'
lua.properties and it should behave as expected. Anything set in
global.properties can be overridden in lua.properties when it is loaded
for Lua files.
style.lua.1=$(colour.code.comment.box),$(font.code.comment.box),back:#D0F0F0,eolfilled
style.lua.3=$(colour.notused),$(font.notused)
style.lua.8=$(colour.string),$(font.code.comment.box),back:#E0FFFF
Meanwhile, in SciTEGlobal.properties, these lines managed to take global
effects:
if PLAT_WIN
font.base=font:Verdana,size:10
font.small=font:Verdana,size:8
font.comment=font:Comic Sans MS,size:9
Changing the above lines I was able to restore basically the same effect
as it was in the official scite. Now the most puzzling fact is why
settings like $(font.code.comment.box) and font.comment could interfere
with my TeX and metapost settings out of the comment environment?
That I'm not entirely sure without any extra details.
Take care,
-Mitchell;
Thanks and take care
instanton
----- Original Message -----
*From: *mitchell <mailto:[EMAIL PROTECTED]>
*To: *scite-interest <mailto:[email protected]>
*Sent: *2007-06-09, 07:12:14
*Subject: *[scite] Re: Feature request: multicolumn tools menu or
hiddenmenuitems
Hi,
> Is there any simple way to make
> the keys.lua interface work in the official SciTE? What is the
minimum
> requirement to make them work if some part of the source has to
be modified?
Modify the SciTE extension interface to add support for OnKey. You can
do a diff of SciTE-tools SVN and SciTE CVS to find the differences.
Take care,
-Mitchell;
------------------------------------------------------------------------
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
