CambridgeSoft   Schrodinger   CrystalMaker   EndNote   Systat 
  ´º½º     ¼ÒÇÁÆ®¿þ¾î     ÇÑ±Û È¨ ÆäÀÌÁö     ±â¼úÁö¿ø     È¸»ç     ÁÖ¹®     ÁúÀÇ/ÀÀ´ä  
WinEdt Logo (3 KB)
  WinEdt Ȩ | ¸ÞÀϸµ ¸®½ºÆ® | ¼Ò°³ | Snapshots | ÁÖ¿ä »ç¾ç | °¡°Ý/ÁÖ¹® | ¼³Ä¡ ¿ä·É | ´Ù¿î·Îµå  
  WinEdt Ȩ < WinEdt ¼Ò°³ < Known Problems

Known Problems

Although I would prefer this page to be empty it is very unlikely that this will ever become the case. There are two kind of problems: reproducible and non-reproducible ones. Furthermore, some problems are directly related to bugs in WinEdt and can be fixed, while some oddities in WinEdt's interaction with other accessories are not necessarily WinEdt's fault. So far I've managed to fix or find a way around all the reported problems that could be reproduced on my machine. I am planning to maintain this record.

There are, however, two instances that have been reported in a few (much less than 1%) cases and so far I am helpless when it comes to reproducing or diagnosing the problem. Apparently, on some (Win95) systems WinEdt's common dialogs (Open, Save As...) disappear after another Win32 application has been launched. In one instance the problem is consistent while in another case it is frequent but not always reproducible. In spite of making a few test versions I still don't know what goes wrong. Anybody with a similar problem should send me a report containing as many details about your Windows and computer as possible. Maybe I'll get enough information to guess what do this systems have in common.

I've also received a report claiming that after starting WinEdt, Explorer crashes and all TRS in the Task Bar disappear. WinEdt and Windows appear to be operating normally after the crash. I cannot reproduce this crash and will have to get more feedback to diagnose the problem.


If you are experiencing a problem similar to the above described oddities you should send me a report containing as many details as possible. Details such as other applications running when the problem occurs, your version of Windows, system resources at the time of the crash are all very valuable when it comes to correctly diagnosing the problem.

It would help if you download the following generic MDI application compiled in Delphi (without a single line of custom code). In particular, I would like to know if the problem persists for this application or does it appear to be WinEdt specific. WinEdt 5 is compiled with Delphi 5 (pro).

WinEdt Ȩ | ¸ÞÀϸµ ¸®½ºÆ® | ¼Ò°³ | Snapshots | ÁÖ¿ä »ç¾ç | °¡°Ý/ÁÖ¹® | ¼³Ä¡ ¿ä·É | ´Ù¿î·Îµå
Copyright ¨Ï 1998-2008 by Aleksander Simonic (alex@winedt.com). All rights reserved.
 È¨ ÆäÀÌÁö | ¼ÒÇÁÆ®¿þ¾î | ÇÑ±Û È¨ÆäÀÌÁö | ±â¼úÁö¿ø | È¸»ç | ÁÖ¹® | ÁúÀÇ/ÀÀ´ä