Note: The project file (*.ppj) version is different, so once loaded in 4.0 they will not load in any previous version.
Changes from Beta 4 to Beta 5:
* bugfix: another case when the project output directory wasn't created by the IDE - the logic is now revised.
* bugfix: switching from a source code window to another window, and back again, would reset the caret position when positioned at an "indent point".
* bugfix: the POCRT.DLL startup code failed on Windows 9X.
* bugfix: unreferenced parameters in fastcall functions were counted as stack-based parameters by the compiler (so the emitted return instruction could be wrong).
* bugfix: leaving a _except block with an unconditional goto gave the compilers "unreachable code" detection huge problems.
* Added C runtime functions _stristr, _wcsistr, _strichr, _wcsichr, _strrichr, _wcsrichr, _memichr and _wmemichr.
* Added a missing definition to winspool.h (PRINTPROCESSOR_CAPS_1).
* A little more tweaking of the C parser in the browse info builder (pobr.dll).
Changes to version 4.00:
http://www.smorgasbordet.com/pellesc/changes_300_400.htm
Main setup:
http://www.smorgasbordet.com/pellesc/400/setup.exe
Add-in setup:
http://www.smorgasbordet.com/pellesc/400/setupsdk.exe
Pelle
Thanks.
John
Beta #4 and Version 4.00.43 is shown in IDE? Is that correct?
Quote from: "real"Beta #4 and Version 4.00.43 is shown in IDE? Is that correct?
No - should be Beta #5, version 4.00.46...
Pelle
:mrgreen: Is there is chance to be able to dock the tool window in the ressource editor ? :oops: please :wink:
Best regard
Philippe Clec'h
PS : I like to use a font called "Bepa" & "Bepa Mono" but when i select this one the display is corrupted between lines. If you want i can attach these fonts to let you find why this happen :)
Thanks Pelle.
Quote from: "Pelle"
No - should be Beta #5, version 4.00.46...
Pelle
Sorry, at home I also realized it. Here (at work) we use a proxy and cause I'm no proxy-administrator I will not be able to flush the cache. And it's seems that in that cache beta #4 remained :evil:
I fear you don't want to change the name of setup.exe to setup{version}.exe... :?
Hi Pelles :D
I have a little trouble with the command line argument. I want to use something like -I$DATAS\import\ but when i process the argument i got this : DATAS\import\. It seem that $ hide the next char to it :-/. Is it a bug or did i have miss something :mrgreen:
Best regard
Philippe
Quote from: "ernest33"Is there is chance to be able to dock the tool window in the ressource editor ?
I really hate dockable windows myself - probably not...
Pelle
Quote from: "ernest33"Hi Pelles :D
I have a little trouble with the command line argument. I want to use something like -I$DATAS\import\ but when i process the argument i got this : DATAS\import\. It seem that $ hide the next char to it :-/. Is it a bug or did i have miss something :mrgreen:
Best regard
Philippe
The
$ character signifies the beginning of a project macro, and is reserved for this purpose. There is no "escape" for this - at least not for now...
Pelle
Quote from: "real"I fear you don't want to change the name of setup.exe to setup{version}.exe... :?
Not sure I can easily make it automatically - which means a manual change, which probably means I will forget it at some point...
Pelle
...i'll wait to see the future version... :shock:
Philippe