Known Bugs in CREdit 1.013


 
The active script engine, if used, cannot be properly initialized sometimes. This mainly occurs under WinXP or 2K.
Due to 64KB size limit for Windows INI files, the CREditHgl.ini file cannot be bigger than 64KB. If it is, it's truncated.
A lot of people have complained that the cursor position is not correct when editing HTML files (the default syntax highlighting of these files uses bold to mark the HTML tags). The reason for this is in the different width of the 'normal' and 'bold' characters in some fonts.
Solution: turn off the bold keywords, or use fonts like Courier New which do not have this problem.
If you start CREdit several times from the command line, it will 'remember' the directory where the first instance was started, and will use it to open the next files.
If you configure a tool with argument that is enclosed in quotes (as in "$(FileDir)"), the quotes will be lost after you restart CREdit.
A temporary workaround is to add a dummy argument on the command line, e.g. "$(FilePath)" -dummy.
If you switch off the Tab Pane and then use Print Preview, the Tab Pane will pop up again.
CREdit will not correctly import syntax files with keyword lines longer than 4096 chars.
Selecting a column and pressing Tab or Shift+Tab (i.e. trying to indent or unindent it) may sometimes crash the editor.
Trying to assign Python as scripting engine will crash the editor. (It seems that Python doesn't like my TLB...)
ActivePerl cannot access the $Application object. The macro names can not be determined.
 

Go to the Current Release page.