"Márton Balázs" | 1 Apr 2004 21:49
Picon
Favicon

Re: Filerx

Hi Laurent!

> Filerx looks for SciLexer.dll through a  LoadLibrary("SciLexer.dll").
> This dll should be in the same directory as Filerx or in the system
> directories, in order to be found..

Thanks for your personal answer, I fixed it, and now everything is O.K.

Greets:
Balázs

_____________________________________________________________________
Austin Hastings | 1 Apr 2004 05:19
Picon
Favicon

Newbie Q: How to remap characters in keyboard mapping? (Plus some whining)

Howdy, troop.

The primary question:

Sorry if this is common knowledge, but Google couldn't find it for me.

I'm trying to do a couple of keyboard remappings on Scite under Windows
2000:

1- Ctrl+ left/right -> SCI_WORDPARTLEFT/RIGHT
2- Shift+ ...       -> ...
3- Alt+ left/right  -> SCI_WORDLEFT/RIGHT

and

4- Shift+Space      -> _ (underscore)

I've got the first two working okay using the SCI_ #define constant values
(2390..2393).
I cannot get the Alt+left, etc., keys to respond using the same approach.

Finally, there doesn't seem to be any "insert other character" function, so
I tried using 95 (ascii for '_') to no avail. Is there any way to remap a
"plain old key" like this?

Secondary Questions:

1.
The line-oriented commenting feature colorizes only "to end of line" -- it
does not seem to honor eolfilled coloration, so that a block like:
(Continue reading)

Bruce Dodson | 2 Apr 2004 00:43
Picon
Favicon

Re: Re: Lua update

Yes, I merged this into SciTEKeys::ParseKeyCode, and also
your additional numeric keypad keys.  What I didn't do is
update the key parser for user.shortcuts, which is a
separate implementation

For now, let's change the user.shortcuts / language menu
parser in SciTEWin.cxx to just this:

inline bool KeyMatch(const SString &sKey, int keyval, int
modifiers) {
 return SciTEKeys::MatchKeyCode(
   SciTEKeys::ParseKeyCode(sKey.c_str()), keyval,
modifiers));
}

And similarly change SciTEGTK.cxx.

Later on, if someone is interested, user.shortcuts and the
language menu could be changed so the ParseKeyCode happens
in advance and is cached.  (I don't plan to do that; the
computers I use are all fast enough that it makes no
difference to me.)

Bruce
Mike Wuetherick | 2 Apr 2004 01:05

Re: Filerx

is there a seperate forum for filerx, or is it ok to post questions 
about it here?

just curious, i've been experimenting with it for a while and might have 
a few questions at some point.

thanx

mike w
www.gekidodesigns.com
Neil Hodgson | 2 Apr 2004 11:44
Picon

Re: Re: Filerx

Mike Wuetherick:

> is there a seperate forum for filerx, or is it ok to post questions 
> about it here?
> 
> just curious, i've been experimenting with it for a while and might have 
> a few questions at some point.

   It is OK to talk about Filerx here.

   Neil
Neil Hodgson | 2 Apr 2004 11:59
Picon

Re: Slow lexer - On Idle Colourizing/Lexing

Christof Engel:

> I am thinking at the moment how to improve our very slow ABAP lexer. I am
> thinking about starting the lexer delayed in Editor::Idle.

   How slow is it? Lexers are generally very fast. Even ones that backtrack
as LexPerl does to cope with here documents. Is it slow because you have
turned on wrapping and so the whole file is relexed more often?

   Neil
Neil Hodgson | 2 Apr 2004 12:02
Picon

Re: Indent config question

Charles,

> I have a (hopefully) simple question.  I have been trying
> to use the "indent.maintain.filepattern=1" variable in
> SciTEglobal.properties to automatically indent blocks of
> wrapped text.

   Automatically wrapped text is always displayed starting at the left
margin. The indent.* settings are effective when you press Enter to end a
line of text.

   Neil
aBe P | 2 Apr 2004 11:54

php folding bug

I found this code gets folded incorrectly:

   if(isset($_REQUEST['searchA']['boat_id']) && 
$_REQUEST['searchA']['boat_id'] > 0) {
     $boat_infoA = queryRow("SELECT * FROM boats WHERE 
id={$_REQUEST['searchA']['boat_id']}");
     $boat_info = '';
     foreach($boat_infoA AS $k => $v) {
       $boat_info .= "$k => $v<br/>";
     }
   }

Because the first "{" is matched with the "}" at the end of the second 
line.
(Using version 1.59 on Win32)

On the other hand, when I place the cursor after the first "{" the correct 
"}"
gets highlighted. (I guess they parsing and this highlighting use different
routines)

It's not annoying, but maybe someone wants to fix it on the future?

Greetings,

aBe
Philippe Lhoste | 2 Apr 2004 18:56
Picon

Current changes

Recently, I have done a number of changes to Scintilla and SciTE. Most are minor, 
some are unfinished, but overall, the given set of changes is stable: I use daily 
SciTE with these changes.

The Zip file with the changed files can be found on Scintilla's FTP (for Neil) and on 
my French site (CurrentSciChanges.zip).

Here is the list of changes:

### Scintilla ###

Bad transition and number matching:
     \include\SciLexer.h
     \include\Scintilla.iface
     \src\StyleContext.h/cxx
     \src\LexCPP.cxx
     \src\LexLua.cxx
     \src\LexPOV.cxx
     \src\LexVB.cxx

Optimisation:
     \src\CellBuffer.h/cxx
     \src\Document.h/cxx

Rectangular selection at end of line:
     \src\Editor.h/cxx
         Unfinished.

LexLua.cxx
     Folding on repeat/until, and on literal strings & block comments.
(Continue reading)

Neil Hodgson | 2 Apr 2004 23:21
Picon

Re: Newbie Q: How to remap characters in keyboard mapping? (Plus some whining)

Austin Hastings:

> I've got the first two working okay using the SCI_ #define constant values
> (2390..2393).
> I cannot get the Alt+left, etc., keys to respond using the same approach.

   IIRC this was fixed after 1.59 so is in CVS.

Alt+Left|IDM_PRINT|\
Shift+Space|IDM_PRINT|\

   Both work for me.

> Finally, there doesn't seem to be any "insert other character" function,
so
> I tried using 95 (ascii for '_') to no avail. Is there any way to remap a
> "plain old key" like this?

   Not currently.

> The line-oriented commenting feature colorizes only "to end of line" -- it
> does not seem to honor eolfilled coloration, so that a block like:
>
>   # fooo
>   # foo
>   # fo
>
> doesn't produce a solid block of color, but rather a ragged shaped flag.
> Multiline comments handle this okay, since the lexer includes the newline
as
(Continue reading)


Gmane