[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[StrongED] StrongED 4.69b6 available
Hi All,
The sixth beta release of StrongED 4.69 can found on the website:
http://www.stronged.iconbar.com/archives/releases/se469b6.zip
A number of bugs have been found in 4.69b5 that were serious enough to
warrant a new beta release.
Because of this the stable release of StrongED 4.69 will be delayed by a
week or two.
As always, all feedback is welcome and appreciated!
Cheers,
Fred.
Changes in StrongED 4.69b6 (from 4.69b5)
========================================
- Fixed bug in ConfigIO which could lead to 'bad flexblock' error. I'd
seen this before occasionally but recently came across a reproducible
case that allowed me to fix this.
- Fixed 'Save to UserPrefs'. Due to some internal reorganising,
detecting if a default config file was about to be saved failed.
The mechanism behind has changed too, now it always warns when a file
from Defaults is being saved. Previously it would only warn when no
copy was present in UserPrefs.
If you open a file from Defaults and, when asked, tell StrongED to
save it to UserPrefs then a file already present in UserPrefs will be
overwritten. It is therefore very important to use StrongED
mechanisms to open config files, don't open them using the Filer!
- Fixed comment colouring - due to mode flags having been moved round
in order to support the new permissions, comments starting inside a
string weren't ignored.
- Bracket matching didn't honour the quotechar so escaped quotes were
taken as end of string. If the string had a bracket further on it
would be considered 'live'.
- Fixed bug in Search. Constructs like {~"/" .}+ could cause a freeze
when end of scope was reached.
- External edit code passed wrong rule type to ModeWhen code. Because
of this trying to load an external edit file into a specific mode
failed.
- SmartIdent info wasn't being purged when mode was reparsed. Didn't
seem to do much harm but I've fixed anyway.
--
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx