Neil Hodgson | 1 Jun 01:30 2006
Picon

Re: Scintilla 1.69 released

Greg Smith:

> |   Don't call it a selection margin type as that implies the other
> |margin types shouldn't be capable of selection.
> I'm taking this as a possible yes...
> Would you accept a patch with SC_MARGIN_SPACER(3) that did this (or your
> suggested name)?

   I was actually leaning towards allowing a colour to be specified as
that allows various borders to be drawn although we can always add
more margin types such as a dotted line to look like this:
http://www.actiprosoftware.com/Products/DotNet/SyntaxEditor/Default.aspx
   So implement SC_MARGIN_SPACER.

> I have tried to achieve the line selection effect with the folding margin by
> detecting clicks on margin lines without a fold point and then selecting the
> line. This does work for a single line, but you cannot extend the selection
> with the mouse pointer.

   Doing so would make this more messy than I like. You could
implement this by subclassing Scintilla to get first look at all mouse
events.

> Even if this did work, it would not be a complete
> solution as users can choose to hide the folding margin, and I allow setting
> break points by single clicks on the remaining margin, so this is not
> available for line selection.

   If users choose to hide things then they will get less convenient
access to features: even with all margins hidden, triple-clicking
(Continue reading)

Greg Smith | 1 Jun 12:16 2006
Picon

RE: Scintilla 1.69 released

>   So implement SC_MARGIN_SPACER.
Done. I have taken the "least change" approach, and added a new bool to
MarginStyle(). The code changes are small, and all the users like it.

However, it occurred to me (seeing you mentioned the idea of drawing a line)
that there is another way to implement this in a 100% backwards compatible
way.

We could make the second argument to SetMarginTypeN call a set of flags,
then you could have:

SC_MARGIN_SYMBOL = 0	// as now
SC_MARGIN_NUMBER = 1	// as now
SC_MARGIN_SPACER = 2	// STYLE_DEFAULT background
SC_MARGIN_LINERIGHT = 4 // draw line on right of margin
etc

Do you have any preference for implementation? I can send you the changed
files either way.

Greg
Neil Hodgson | 2 Jun 14:26 2006
Picon

Re: Scintilla 1.69 released

Greg Smith:

> We could make the second argument to SetMarginTypeN call a set of flags,
> then you could have:
>
> SC_MARGIN_SYMBOL = 0    // as now
> SC_MARGIN_NUMBER = 1    // as now
> SC_MARGIN_SPACER = 2    // STYLE_DEFAULT background
> SC_MARGIN_LINERIGHT = 4 // draw line on right of margin
> etc

   Sticking the first flag just after an enumeration is rather
constraining. For the line, I would have defined another type like
SC_MARGIN_SPACER and filled that margin with a line drawing colour
(probably STYLE_DEFAULT.fore). Then the client code may define light,
dark, or grey lines or areas independently. If there are flags then it
should be at, say, 16 or 32 to allow expansion of the enumeration
part.

   Neil
Greg Smith | 2 Jun 15:25 2006
Picon

RE: Scintilla 1.69 released

Neil wrote:
>   Sticking the first flag just after an enumeration is rather
>constraining. For the line, I would have defined another type like
>SC_MARGIN_SPACER and filled that margin with a line drawing colour
>(probably STYLE_DEFAULT.fore). Then the client code may define light,
>dark, or grey lines or areas independently. If there are flags then it
>should be at, say, 16 or 32 to allow expansion of the enumeration
>part.
OK, I think I got it. Something like:
SC_MARGIN_SYMBOL = 0    	// as now
SC_MARGIN_NUMBER = 1    	// as now
SC_MARGIN_TYPEMASK = 0x1f	// Mask for allowed types	

SC_MARGIN_SPACER = 32    	// STYLE_DEFAULT background
SC_MARGIN_FILLER = 64 	 	// STYLE_DEFAULT foreground
SC_MARGIN_TYPEFLAG = 0xffffffe0

If you confirm that this is OK, I'll get on and do it.

Greg
SourceForge.net | 2 Jun 05:22 2006
Picon
Picon

[ scintilla-Feature Requests-1499273 ] saved session with folding state + bookmark

Feature Requests item #1499273, was opened at 2006-06-01 20:22
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=352439&aid=1499273&group_id=2439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: saved session with folding state + bookmark

Initial Comment:
I would like to see

1) any user adjusted folding state and,
2) any user bookmarked lines

to persist into a saved session (.ses) so upon next
session open/reload, all previously info are restored. 

Anyone aware of any editor that does this at the moment??

----------------------------------------------------------------------

You can respond by visiting: 
(Continue reading)

SourceForge.net | 2 Jun 16:47 2006
Picon
Picon

[ scintilla-Bugs-1499580 ] REBOL lexer syntax highlighting

Bugs item #1499580, was opened at 2006-06-02 07:47
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102439&aid=1499580&group_id=2439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: SciTE
Group: Bug
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: REBOL lexer syntax highlighting

Initial Comment:
>From user at: bugalugstoo <at> yahoo.com

SciTE 1.69 is the version in question. See attached PNG 
image "SciTE_REBOL_sample.png" for example of where the 
REBOL lexer fails to account for the CHAR datatype. All 
characters after the trailing " are treated as 
belonging to the SciTE properties file. Note the 
correct parsing of the comment in green in the previous 
line.

----------------------------------------------------------------------

(Continue reading)

Neil Hodgson | 5 Jun 07:41 2006
Picon

Re: Scintilla 1.69 released

Greg Smith:

> OK, I think I got it. Something like:
> SC_MARGIN_SYMBOL = 0            // as now
> SC_MARGIN_NUMBER = 1            // as now
> SC_MARGIN_TYPEMASK = 0x1f       // Mask for allowed types
>
> SC_MARGIN_SPACER = 32           // STYLE_DEFAULT background
> SC_MARGIN_FILLER = 64           // STYLE_DEFAULT foreground
> SC_MARGIN_TYPEFLAG = 0xffffffe0

   No, that's even more complex. The 'flags' sentence was conditional:
if you don't need flags then don't add them. How about

SC_MARGIN_SYMBOL=0
SC_MARGIN_NUMBER=1
SC_MARGIN_BACK=2
SC_MARGIN_FORE=3

   Neil
SourceForge.net | 5 Jun 03:09 2006
Picon
Picon

[ scintilla-Bugs-1500687 ] Find mark question when printing

Bugs item #1500687, was opened at 2006-06-05 01:09
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102439&aid=1500687&group_id=2439

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Scintilla
Group: Bug
Status: Open
Resolution: None
Priority: 5
Submitted By: JeffreyRen (jeffreyren)
Assigned to: Nobody/Anonymous (nobody)
Summary: Find mark question when printing

Initial Comment:
When you enable "find.mark" Scite v1.69, and select a 
pdf printer, the find mark area will become a light-
red area. And sometimes, the part of last letter will 
be out of this area.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=102439&aid=1500687&group_id=2439
Greg Smith | 5 Jun 11:03 2006
Picon

RE: Scintilla 1.69 released

OK,

SC_MARGIN_SYMBOL=0
SC_MARGIN_NUMBER=1
SC_MARGIN_BACK=2
SC_MARGIN_FORE=3

It shall be.

Greg
Iago Rubio | 5 Jun 16:37 2006

SciTE license

SciTE is being added to the fedora-extras repository - thanks to  Jorge
Torres who's packaging it - and there are some doubts about its license.

I pointed out that SciTE and scintilla are licensed under the Python
license, but there are other opinions such as the MIT license and  the
"Historical Permission Notice and Disclaimer" as it seems is stated on
the Wikipedia.

http://en.wikipedia.org/wiki/Scite

So this mail is to request an authoritative answer from Neil on what
license tag should be used in the SciTE package.

Thanks in advance.
--

-- 
Iago Rubio <iago <at> iagorubio.com>

Gmane