SynWrite (Syn2)

Matthias030 · Post by *Matthias030 » 2010-08-07, 07:25 UTC

In new document type any word and enable word wrap. Set cursor to beginning of document. Now hold TAB or SPACE key until word is moved to line 2. Word is fixed at beginning of line 2. You can not move it again. But in status bar you see that position is still increased.

Unfortunately the same in ecdemo.

Alextp · Post by *Alextp » 2010-08-07, 08:14 UTC

Yes, strange behaviour.

Alextp · Post by *Alextp » 2010-08-07, 09:06 UTC

Btw issue with keys(Ctrl-shift-P) may resolve when i make Menu. Menu hotkeys will override current hotkeys.

Matthias030 · Post by *Matthias030 » 2010-08-07, 11:33 UTC

sounds good. also Ctrl+P is still not working in read only mode.
Ctrl+1 - Ctrl+7 for jump to bookmarks could be fixed too in RO.

Matthias030 · Post by *Matthias030 » 2010-08-09, 14:31 UTC

Here is only a small issue I just found out:
In an empty html or php file (0 bytes) open autocomplete by pressing ctrl+space. You got an exception. Css files are ok.

Alextp · Post by *Alextp » 2010-08-09, 15:21 UTC

fixed. Also fixed: on empty line (htm) call ACP: it adds tag without <. Now < added if previous char is not <.

Matthias030 · Post by *Matthias030 » 2010-08-09, 16:02 UTC

I have just tested autocomplete in empty lines. I have never done that before.
There is another issue in autocomplete in empty lines: by selecting tag by mouse tag is entered twice. affected are html, php and css
If you enter autocomplete in html and click on first tag "<a>" then entered is "a a".

Alextp · Post by *Alextp » 2010-08-09, 16:51 UTC

fixed (seems), see beta.

Matthias030 · Post by *Matthias030 » 2010-08-09, 17:35 UTC

In beta I get exception at program startup if ruler bar is enabled

Matthias030 · Post by *Matthias030 » 2010-08-09, 17:43 UTC

In empty file open autocomplete by pressing ctrl+space. You got an exception: FIXED
selecting tag by mouse, tag is entered twice: Fixed

A new issue: In htm press CTRL+Space. Now type "bo" to browse to body-tag. Autocomplete list is not changing tags. Old beta was ok.

Matthias030 · Post by *Matthias030 » 2010-08-10, 08:43 UTC

A suggestion for toggle non-printable characters:

For all encodings except OEM these chars are used
Space: ansi char code 183 "· "
Tab: ansi char code 155 "›"

For OEM it is used:
Space: OEM char code 183 "À"
Tab: OEM char code 155 "ø"

Ansi code 183 "· " is equal to OEM char code 250 "· "
Ansi char "›" does not exists in oem table, so I suggest to use char "»" instead.

All except OEM:
Space: ansi code 183 "· "
Tab: ansi code 187 "»"

OEM:
Space: oem code 250 "· "
Tab: oem code 175 "»"

Alextp · Post by *Alextp » 2010-08-10, 09:55 UTC

Ok: just
oem code 175 "»"- not Ok for Russian table, it's "п" char. I use > instead..

Matthias030 · Post by *Matthias030 » 2010-08-10, 11:01 UTC

Ah ok. I didn't tried russian table.

Matthias030 · Post by *Matthias030 » 2010-08-10, 12:12 UTC

Here a few more things related to encoding and characters:

1. Not really important: When using for example Ansi<->OEM and select "changing encoding for the modified file" then char info in status bar for current char is not refreshed.

2. By clicking on char info in status bar, current char could be selected in char table if possible. Good for Ansi, OEM, KOI8. Not possible for Unicode, UTF-8 because char codes are not in table.

3. When you make main menu then option for "Convert encoding to..." would be useful. This is the same as making any change in file and select "changing encoding for the modified file".

Converting does this:
OEM char #169 "®" -> Ansi char #174 "®"

Only changing encoding does this:
OEM char #169 "®" -> Ansi char #169 "©"

Alextp · Post by *Alextp » 2010-08-10, 13:42 UTC

Agree. Making 1, 2- useful. 3- later(when menu will be).