However, i call time-out on the (major) feature addons. I suggest 'feature freeze' (or close to it), where bugs get squashed, and only bugs get squashed. Feature requests will be noted, and slated for the next release. When that release enters feature freeze, any requests after that is relegated to the NEXT release agian. and so on.
(the more observant people may notice that this is is a remarkably common release cycle in the F/OSS community. This is no coincidence, as it makes a great deal of sense.)
-----bug list last updated 2006-09-04
serious bugs:
- winbuilder.exe locks up when launching processes through 'ShellExecute'.
- The ui editor has issues when trying to edit the properties of the control you just edited. This only happens if you click the canvas in between edits. So: edit control -> click canvas -> edit control: error; edit control 1 -> edit control 2 -> edit control 1: works. The current workaround is to select another control (than the one you wish to edit) first.
- winbuilder's interface does not like a DPI setting of anything else than 96
not so serious:
- A lot of the strings need editing for accuracy and clarity. No offense, nuno, but you are very clearly not a native english speaker
- the "open" button did not have a bevel (in beta4)
- the interface does not follow Windows' native color scheme.
----------
a few bugs there. And they all annoy me
I also have some suggestions regarding the interface in general, but that's not for this thread.I'll volunteer for editing the string '.rc' files or whatever (localizeable strings DO exist outside the main source i hope?) seeing as I AM a native english speaker (well, i am norwegian, but my old man is american) and quite good at writing. I even get capitalization sometimes
.//martin
