well done, now FASMW is stable

i saw that richedit control virtually splits long lines into 3kB (3072 chars) parts. that technique improves performance, especially with non-fixed-width fonts. also i think that this behaviour will reduce memory space requirements with that long lines, but who cares? - i haven't found any assembly sources with that long lines

actually my programs are generally small, so i don't need any debugger. but who know what will happen in future?

according to thread subject: i think that code completion should be implemented only in fresh, because FASMW is only an integrated 'notepad' and should be simple. don't blame me, this is only my suggestion

This perfectly reflects my stand.

However FASMW from the beginning was planned to integrate the source-level debugger, too - that's why it always has been 0.9x, since this planned feature has not yet been done.

Well, fasmw's editor internally splits the lines into 240-character segments (does this number remind something to you? ) - this control was originally designed for high performace, as I was initially developing it on a quite old computer (Pentium 60; well, it was an ultra-fast machine when it was bought), and I still use it there sometimes.

universal is always huge, slow, buggy and, finally, not universal in real

Wow, that's great news to me. May I ask, have any work been done for having this 1.0 release soon?

Designing mainly. It has been a few times that I dropped completely the existing design for source level debugger before even starting to implement it. For example the line offset collector used by unofficial listing extension is not good, and not enough for the debugger purposes. Actually it can even be fooled and "exploited" in some way, when additional pass it does to collect line offset doesn't generate the same output as the "regular" last pass, and thus generate the bad output; but that's another story... For those reasons (and also a few other) the listing extension stays unofficial, and the source level debugger stays not written. Nevertheless I've already got the ideas, how to do it well, and thus you can expect I will start working on the debugger soon (when only I have time for this) - as I don't plan touching the core of the assembler too much in the near future, and instead wanted to concentrate on two tasks: improve documentation for assembler and finish the IDE. Also the separation of edit control into core and interface in the similar way, as it was done with the assembler, was done to allow building on this core the analogues of fasmw for other operating systems.
So my fasm-related programming efforts may go mainly into direction of developing the IDE(s), though it's also possible that as a side-effect of implementing the debugger into IDE, there will be also added support for some debug info formats in the assembler.
The all mentioned above actually makes my complete to-do list for flat assembler as for now.

I downloaded lastest fresh and can't get it work. Could you please help me?
Also, I don't know how to add events to buttons I add in form designer. Does fresh use some kind of framework for RAD or it's just a resource editor like in RADasm?

Thanks!