**
than you should've wrote that on bug report. When you wrote fixed and flagged fixed I naturally assumed all fixed (when this bug reported there was no trash to test).

Not really an error. Maybe i'm just stupid. But ...
I think, it's time that after the functionality changed, that also the desciptions reflect that change.

Are you sure this is a good idea?
Shell Folders are the ones that belong to the AllUsers profile.

I got it!

I'm going to fix.

Peter

Those error reporting routines of WB are a great help!
It's just not possible to read through all scripts line by line.

Empty (acedemic) key creation (acedemic=DO NOT use unless you know what you are doing)
RegWrite,HKLM,<typ>,<Key>, ==>keys with null value
RegWrite,HKLM,<typ>,<Key>,<Value>

Just wondering if you fixed Lancelot's issue of file extraction to desktop in scenario where user profile doesn't reside on %SystemDrive%?

lib := GetEnvironmentVariable('SystemRoot') + '\system32\shell32.dll';

  h := LoadLibraryEx(PAnsiChar(lib), 0, LOAD_LIBRARY_AS_DATAFILE);

//	21769	"Desktop"

  s := GetEnvironmentVariable('UserProfile') + '\' + getResString(h, 21769) + '\';

Only after i once changed the selected option, WB behaves like what is selected. Guess WB get's initialized with the wrong value for default.

With other words: in the past, wbbug + hojobug = success. Today hojobug=bug. Lets wait wb stable release to discuss this later (I need fixes too ).

Since NaughtyPEs HoJoPe is not the latest version. Would someone please check, if he gets also those nonsense entries.
Somehow the use of WB080 manages to bring a bunch of new registry keys and values.



Those two entries should be type binary, but are type string.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\WB-Setup\ControlSet001\Services\HTTP\Security]
"Security"=hex:01,00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,\
00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,\
00,00,02,00,88,00,06,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,\
05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,\
20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,\
00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,00,00,\
14,00,14,00,00,00,01,01,00,00,00,00,00,05,04,00,00,00,00,00,14,00,14,00,00,\
00,01,01,00,00,00,00,00,05,06,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00,\
01,01,00,00,00,00,00,05,12,00,00,00

Peter are you sure that you've fixed the copyorexpand problem?

[process]

Run,%ScriptFile%,bla,ACLUI.DLL,%source_sys%,%target_win%,NOWARN,PRESERVE



[bla]

CopyOrExpand,#2\#1,#3,#4,#5

Also is it normal to get a bunch of RegHiveUnLoad - Failed after a build stops due to an error?

Autosave reacts like on is selected in options thought ask is.

Ok, here it is.

I've run the whole project again. Used the the option to 'not stop on error' to log all errorous load commands (or the missing unload commands ).
I did get a single error.
How can a single double load lead to, i think 6 'can not unloads'?

Request for RegWriteBinary:

RegWriteBinary,<HKEY>,<KeyType>,<Section>,<Keyname>,<Value>

Reason:
I can not write Thai localization infos to registry:

RegWrite,HKCU,0x0,Software\0TEST\key0

I get

@=hex(0):

is it your design purpose ???? (if it is, fine for me, if it is not ... --> please confirm)

Empty Key creation (in Billy's Regedit way, Registry Editor-->Right Click somewhere on right -->New-->Key)
RegWrite,HKLM,0x1,<Key>

Empty Value creation
RegWrite,HKLM,<typ>,<Key>,<Value>

Empty Default (@) Value creation
RegWrite,HKLM,<typ>,<Key>,<Value>,

Hi Peter,

There's a bug with CopyOrExpand not accepting PRESERVE and NOWARN passed as parameters.

http://www.boot-land...?...ost&p=91067

Thanks,
Galapo.

Next Upload will have the value from registry. Maybe that helps.

RegReadInternal('HKEY_CURRENT_USER', 'Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders',

	'Desktop', S);

s := AnsiReplaceText(s, '%USERPROFILE%', GetEnvironmentVariable('UserProfile'));

function WriteNull(dwType: DWORD): boolean;

  begin

	Result := (RegSetValueEx(

	  Registry.CurrentKey, // handle of key to set value for

	  PAnsiChar(key), // address of value to set

	  0, // reserved

	  dwType, // flag for value type

	  nil,

	  0) // size of value data

	  = ERROR_SUCCESS);

  end;



  function WriteEmpty(dwType: DWORD): boolean;

  begin

	Result := (RegSetValueEx(

	  Registry.CurrentKey, // handle of key to set value for

	  PAnsiChar(key), // address of value to set

	  0, // reserved

	  dwType, // flag for value type

	  PChar(''),

	  0) // size of value data

	  = ERROR_SUCCESS);

  end;

RegWrite,HKCU,0x1,Software\0TEST,1

can you try on your host without using ansireplace

on the registry of freshly installed XP-enu (and tr) (32bit, 64bit etc.) the default values are REG_EXPAND_SZ with %USERPROFILE%, example: %USERPROFILE%\Start Menu

Just a little annoyance, maybe you can fix it too.

This is what i type.


After closing and reopening this is what i get.


Clearly the Linefeed got correctly encoded into the line during save, however while displaying it is ignored.

Thanks, Lancelot. I now understand the difference between variables and macros: variables can never "execute", they just expand content, whereas macros execute. Previously, variables could also execute, but this functionality has been split to new macros.

Hence I think we need a new command: SetMacro. To me it seems there is little advantage in having the difference between a variable and a macro determined by using % or not. So:

Set,%var%,test would set a variable
SetMacro,%macro%,"Run,%ScriptFile%,test" or SetMacro,%macro%,Run#$c%ScriptFile%#$ctest would set a macro.

WB would then have two separate stacks, variables and macros. A variable could be turned into a macro:

[variables]

   %var%=Run,%ScriptFile%,test

   

   [process]

   SetMacro,%macro%,%var%

   %macro%,yes!

   

   [test]

   Echo,#1

This leads me to suggest that if WB splits variables and macros at the stack level, then logically it also needs to split this at script level. That is, we can't have macros under [variables]. Macros need to be listed under a new [macros] section. Eg:

[variables]

   %section%=1

   

   [macros]

   test=run,%scriptfile%,%section%

   

   [process]

   test,yes!

   

   [1]

   Echo,#1

What do you think?

Regards,
Galapo.

I think that cannot.

Reason: formally text defined in [Variables] replaced this text, whenever it appeared inside a line.

That lead to several bug reports.

Therefore starting with 075 's new variables handling [Variables] without the % are only replaced when they are the first element in a script line. Then they mean some shortcuts to other commands (like used in the API) and are called 'macros'

Peter

[variables]

 test=run,%scriptfile%,%section%

 %section%=1

 

 [process]

 test,yes!

 Set,%section%,2

 test,great!

 

 [1]

 Echo,ONE:#1

 

 [2]

 Echo,TWO:#1

Also is it normal to get a bunch of RegHiveUnLoad - Failed after a build stops due to an error?

[Process]

RegHiveLoad,WB-Software,%target_sys%\config\software

RegHiveLoad,WB-Default,%target_sys%\config\default

RegHiveLoad,WB-Setup,%target_sys%\setupreg.hiv

RegRead,HKLM,%WB-Setup%\PSCC,Command0,%var%

RegHiveUnLoad,WB-Software

RegHiveUnLoad,WB-Default

RegHiveUnLoad,WB-Setup

I'm not sure that's the best idea. I think it is better that if 080 is not going to be backwards compatible,
//then we should get such things out of the way now before release.
//Then we don't have to introduce [macros] in 081 or 082 and break compatibility again and have to do a mass ...

Regards,
Galapo.

In the last days with rather complicated variables the question came up that WinBuilder's variables handling sometimes fails.

Here a short explanation what can be done and what cannot be done.

First some rules:

• WinBuilder Script Line Parameters are separated by a comma.
  If a comma is inside an argument, it must be 'escaped' by #$c
• Besides some special cases (e.g. parameters in ShellExecute) generally enclosing quotes are not needed.
• Enclosing quotes MUST be used if the WinBuilder Script Line Parameters contain spaces
  If the spaces are replaced by the escape #$s, the enclosing quotes should be ommitted.

In most cases user violation of that rules are accepted by WinBuilder and processed as assumed.
E.g. unnecessary enclosing quotes or a comma inside an item enclosed by quotes.

But sometimes that can bring unexpected results.

As far as i understand, since 0x1 can add only 1 value, than all values after 5th comma whether between quotes or not, are used as a single value by winbuilder ?????

Peter you've fixed the wrong part at the autosave problem.
The default used to be ASK. Now it is ON.

Actually sad, thought the good thing about wb is it flexibility ...

RegAddMulti,HKLM,Section,Key,APPEND,String

   RegAddMulti,HKLM,Section,Key,PREPEND,String

   RegAddMulti,HKLM,Section,Key,BEFORE,SubVal,String

   RegAddMulti,HKLM,Section,Key,BEHIND,SubVal,String

   RegAddMulti,HKLM,Section,Key,PLACE,Index,String

   RegAddMulti,HKLM,Section,Key,DELETE,SubVal

A new version is uploaded.

First: One change may bring some work to adapt some lines of code:
I renamed RegAddMulti to RegMulti.
Reason: Because it also performs non-adding tasks like Delete and Index, the 'Add' in the name may be confusing.

Second: I added the first version of a syntax description to trash.zip.
Nuno suggested, from now on to have manuals which version dependent only show new / changed functionalities.
The sysntax description is the first of these 'Incremental' manuals.


Peter

BEFORE and BEHIND make it possible to put a string more the once in a MULTI_SZ.

Is it feasible to check whether the string already exists and if so delete it and then write it back in to the position indicated by the command? Or is it better to just warn in the log and if a script needs a particular ordering then it should you 'DELETE' and then the other desired command, say 'PREPEND' or 'BEFORE'?

Regards,
Galapo.

[process]

RegHiveLoad,WB-Software,%target_sys%\config\software

RegWrite,HKLM,0x7,WB-Software\PSC,MultiInside1,one,two,three,five,six,seven

If,EXISTREGMULTI,HKLM,WB-Software\PSC,MultiInside1,three,Echo,YES

Else,Echo,NO

If,EXISTREGMULTI,HKLM,WB-Software\PSC,MultiInside1,xxx,Echo,YES

Else,Echo,NO

RegAddMulti,HKLM,WB-Software\PSC,MultiInside1,INDEX,TWO,%var%

Echo,%var%

RegAddMulti,HKLM,WB-Software\PSC,MultiInside1,APPEND,bla

RegAddMulti,HKLM,WB-Software\PSC,MultiInside1,APPEND,TWO

RegWrite,HKLM,0x7,WB-Software\PSC,MultiInside2,one,two,three,five,six,seven

RegAddMulti,HKLM,WB-Software\PSC,MultiInside2,PREPEND,bla

RegAddMulti,HKLM,WB-Software\PSC,MultiInside2,PREPEND,TWO

RegWrite,HKLM,0x7,WB-Software\PSC,MultiInside3,one,two,three,five,six,seven

RegAddMulti,HKLM,WB-Software\PSC,MultiInside3,BEFORE,TWO,bla

RegAddMulti,HKLM,WB-Software\PSC,MultiInside3,BEFORE,XXX,BLA

RegAddMulti,HKLM,WB-Software\PSC,MultiInside3,BEFORE,three,five

RegWrite,HKLM,0x7,WB-Software\PSC,MultiInside4,one,two,three,five,six,seven

RegAddMulti,HKLM,WB-Software\PSC,MultiInside4,BEHIND,TWO,bla

RegAddMulti,HKLM,WB-Software\PSC,MultiInside4,BEHIND,XXX,BLA

RegAddMulti,HKLM,WB-Software\PSC,MultiInside4,BEHIND,three,five

RegWrite,HKLM,0x7,WB-Software\PSC,MultiInside5,one,two,three,five,six,seven

RegAddMulti,HKLM,WB-Software\PSC,MultiInside5,PLACE,2,bla

RegAddMulti,HKLM,WB-Software\PSC,MultiInside5,PLACE,10,two

RegAddMulti,HKLM,WB-Software\PSC,MultiInside5,PLACE,2,two

RegAddMulti,HKLM,WB-Software\PSC,MultiInside5,PLACE,three,blabla

RegWrite,HKLM,0x7,WB-Software\PSC,MultiInside6,one,two,three,five,six,seven

RegAddMulti,HKLM,WB-Software\PSC,MultiInside6,DELETE,bla

RegAddMulti,HKLM,WB-Software\PSC,MultiInside6,DELETE,two

RegHiveUnLoad,WB-Software

To 3rd: I never have a greyed 'Create' button. Can you explain how to reproduce?

Here it is.

This is working with 077rc2:

[Process]

Set,%test1%,"Exec,%ScriptFile%,entry",PERMANENT

%test1%,hello



[entry]

Message,#1,Information

Regards,
Galapo.

[process]

Set,test1,"Exec#$c%ScriptFile%#$centry",PERMANENT

test1,hello



[entry]

Message,#1,Information

But the issue is that this produces a syntax error:

[process]
//Set,%bla%,AnyContents,PERMANENT
Set,%bla%,"",PERMANENT

That is, %bla% has to be defined as "something" before it can be given an empty value.

Regards,
Galapo.

You've change something about the 0x7 registry writes, i've read.
Is this code from 'convert files to script' still ok?

Winbuilder already have an internal function to open script folder (when folder selected at left, by clicking yellow icon at right )

an idea is having a syntax to use this function for anyfolder (because it works better and much proper (and I guess easier and would be faster) than using explorer.exe

just to give example:

explorefolder,%Globaltemplates%\blablaapplication\PutFilesHereFolder

ShellExecute[Ex],Explore,Folder[\FileName][,"Parameters"]

I see you set back old design... (techinically it is not fixed, reverted back to old design). Whatever.....

RegWrite,HKCU,0x1,Software\0Test\testkey,,

This creates

Windows Registry Editor Version 5.00



[HKEY_CURRENT_USER\Software\0TEST\acwfile]

does NOT create

Windows Registry Editor Version 5.00



[HKEY_CURRENT_USER\Software\0TEST\acwfile]

@=""

I get "Variable definition loop" errors with latest trash, tested with LiveXP Recommended

question is, this does not work !!??
ShellExecuteEx,Explore,%scriptdir%
it opens 1 upper directory

This produces a syntax error warning with latest trash:

Set,%testvar%,"",PERMANENT

How do we permanently set an empty variable?

Thanks,
Galapo.

Fixed. no it was not

After 080 published, I will put on bug report with some other things, but I am not sure what will happen when it is flagged as fixed .......

shortly: Case closed for me

My opinion is that Set command should be used for both, but [variables] should not be used for both anymore.

EDIT: Wait some minutes, I have an idea for the script, I have to test.

Hi Peter,

Currently the WB editor wand for CopyOrExpand gives us:

CopyOrExpand,FileToCopyOrExpand,DestinationFolderOrFilename

I wonder if it could supply either

CopyOrExpand,FileToCopyOrExpand,DestinationFolderOrFilename[,PRESERVE,NOWARN]

or

CopyOrExpand,FileToCopyOrExpand,DestinationFolderOrFilename[,NOWARN,PRESERVE]

Regards,
Galapo.

[well, in fact I do not know how to create empty value with latest trash.

If you add "Empty Value Creation Rules" to syntax_rules written above for 0x1 0x2 0x3 and key , we can close regwrite case for wb080 development

[process]

RegHiveLoad,WB-Software,%target_sys%\config\software

Run,%ScriptFile%,do-work,0x1

Run,%ScriptFile%,do-work,0x2

Run,%ScriptFile%,do-work,0x3

Run,%ScriptFile%,do-work,0x7

RegHiveUnLoad,WB-Software



[do-work]

If,EXISTREGSECTION,HKLM,WB-Software\psc#1_1,RegDelete,HKLM,WB-Software\psc#1_1

If,EXISTREGSECTION,HKLM,WB-Software\psc#1_2,RegDelete,HKLM,WB-Software\psc#1_2

RegWrite,HKLM,#1,WB-Software\psc#1_1

RegWrite,HKLM,#1,WB-Software\psc#1_2,,

RegWrite,HKLM,#1,WB-Software\psc#1_1,Key_1

RegWrite,HKLM,#1,WB-Software\psc#1_2,Key_2,

RegWrite,HKLM,0x3,WB-Software\Microsoft\SystemCertificates\CA\Certificates\109F1CAED645BB78B3EA2B94C0697C740733031C,Blob,03,00, ...

Syntax was not valid: [RegWrite,HKLM,"0x1","WB-Software\Microsoft\SystemCertificates\CA\Certificates\109F1CAED645BB78B3EA2B94C0697C740733031C","Blob","03","00", ...

Hi Peter,

I'm thinking here particuarly of '9 - DefineBootsector.script'. Currently it sets a few variables, generally:

Set,%BootSector%,grldr,PERMANENT
Set,%MenuFile_GRUB%,%TargetDir%\menu.lst,PERMANENT
Set,%MenuAdd_GRUB%,"Exec,%ScriptFile%,Add-grub4dos-entry",PERMANENT

This works with 077rc2, now does not work with trash. So no backwards compatibility in this regard? There's a number of scripts which will be broken.

Thanks,
Galapo.

Ok, so if 080 is going to not be backwards compatible in this regard, why don't we just draw the line here and implement even more improved variable and macro handling like I suggested: http://www.boot-land...?...ost&p=90523

In other words, variables and macros should from now on be kept distinct. No writing macros to [variables], this just adds to the confusion. Set,test1,"Exec#$c%ScriptFile%#$centry",PERMANENT shouldn't add to script.project [variables] because it isn't thought of as a variable anymore but a macro -- it should therefore write to [macros].

Regards,
Galapo.

Cathegory checkboxes should be only half-checked (crossed) when not all elements are selected inside it...

Just found myself stuck with this view of WB080 whenever i clicked on the download button. Nothing short of a restart fixed this issue.

You know, I was wondering when you were going to catch on and suggest that! But think about where LiveXP development prodding has got us in this regard: no scripts need to be touched and we have backwards compatibility. I think it's a win-win for both LiveXP and WB.

You do a great job Peter and Lancelot and I are both greatful for your efforts.

Thanks,
Galapo.

Why not simply pass the %RunFromLoc% to a capi call and let CAPI do the rest?

If you and ctmag weren't able to run the stupid Vbox, what would a new user do?

Since the post has been removed, i state it's contensts again.



As a workaround, one can still use the search backward button.

But i really like to ask our development team the question, how it is possible that sooooooooooooooooooo many of the features that worked already fine previously, got broken in this version?
Imo, rewriting WB from scratch, couldn't have created more havoc.

Using Message,%version% just returns 080.

here's an issue with LiveXP. Remember that it has been the project stuck with 077rc2 for a long while. And apart from the macro issue just solved, this was not due to scripts which needed fixing! Nothing changed in the project and now WB starts to work again. (Even the so-called incorrect syntax with macro is back working in latest release, so the scripts in question don't need to be updated in this regard either.) This can only be a good thing.

StrFormat,REPLACE,%RunFromLoc%," ","",%runfrom%

If,Not,%runfrom%,Equal,Rundefault,%runfrom%,True

If,%RunFromLoc%,EQUAL,"Run From RAM",Runfromram,True

If,%RunFromLoc%,EQUAL,"Run From CD",Runfromcd,True

just a reminder. It was found before 080 released during development, was working with "080 initial" , was working with "080 rev1" , than again not working with "080 rev2"

I love the new feature, that i can select and unselct servers before actually connecting to them.
But i had already twice WB telling me, that it can't find any servers and i should check my proxy settings.
I use no proxy and boot-land is accessable just fine.

The other thing, i think needs 'fixing' are the new buttons.
Their position is not logical to me. Shouldn't the buttons be better next to the server list?

Also the overuse of the red X on the downloadpage bothers me a bit.
It means eighter, close, stop or delete. Too much variety for my taste.

• Server List: Remove server
• Project Tree: Stop building tree
• Dialog Head: Leave the dialog

I just opened the download page and imediately got the message.
Clicking on build tree though downloads just fine.
Selected servers:
update.boot-land.net
nativeex.boot-land.net
naughtype.winbuilder.net

ShowError('None of the selected Servers could be accessed!'#13'Perhaps you need to define Proxy access');

"Make sure that yout network cable is plugged in"
"Make sure that your router is swithed on"
...

imo, a sybol should always have only one meaning per page, preferably one meaning per program.

• Server List: Remove server
• Project Tree: Stop building tree

• fixed - bug: Access violation on setting interface variables
• fixed - bug in log.html generating. Loop,BREAK can bring "Index out of bounds" and lets WinBuilder hang
• fixed - IniRead now translates comma in value to escape (troubles with TXTAddLine)

[Process-Compress]

Set,%i%,0

Echo,"CAB compressing files.."

Hi psc,

happy new year,

the link you posted redirects to Winbuilder 078 SP4.

Regards.

• fixed - bug: Unresolved *.Link brought crash with 'invalid filename'
• fixed - bug: Dependencies and Excludes did not work on *.Link files
• fixed - bug: No section shown in log, when started by button
• fixed - removed senceless "Download disabled" message when file exists on "WebGetIfNotExist" command
• fixed - bug in syntax check of "txtAddLine"
• added - optionally run WinBuilder only in CPU / core #1
• fixed - bug: changed ISOFile and TargetDir are not written to script.project

• fixed - bug: double comma when generating updates.ini
• fixed - bug in download when path contained 'Updates'
• fixed - bug in interpreting download levels
• fixed - bug: no download tree on a fresh installation

RegWrite,HKLM,0x7,Section,Key(MultiString),value1,value2

RegWrite,HKLM,0x7,Section,Key(MultiString),value11#$cvalue12,value21#$cvalue22

RegRead,HKLM,Section,Key,%var%

	 RegWrite,HKLM,0x7,Section,Key(MultiString),%var%#$cnewval

RegWrite,HKLM,0x7,Section,Key(MultiString),%var%#$cnewval

RegWrite,HKLM,0x7,Section,Key(MultiString),%var%#$znewval

RegWrite,HKLM,0x7,Section,Key(MultiString),%var%#$znewval1#$cnewval2

[Process]

	  //AddInterface,Filenam,Prefix

	  AddInterface,%FundamentalsScript%,fun

	  Echo,"RAMDiveLetter is: %fun_pScrollBox1%"

I decide to post this new feature of wb078sp2 here since it maybe missed by some of our experienced and new users.
I thought it was a bug but it turned out to be a feature (check here)

As a result:
If you used Download at least once and want to check or download updates of new scripts,
After Clicking Download button, Also click green button upper left.

• They appear only on very few situations
• The changes are coded in just some lines

• Lancelot's / fxscrpt's RegWrite MULTI_SZ issue
• DaveXP's UserAgent issue
• Online's RegWrite 0x3 issue
• ...

[078 SP3]
date=2009-09-25

added - AddInterface command
fixed - Bug ID #214: Deselection by keyboard produces error
changed - New Component Dialog now in center of WB window, rather than in center of desktop
fixed - Deselecting a complete folder containing a mandatory script lets build crash
fixed - Bug ID #222: wb078 sp2 - Depend not working
added - Optional log at WinBuilder exit
changed - In download center, there is an option whether selecting an additional server rebuilds the complete tree.
fixed - bug in RegRead / RegWrite multi_sz
fixed - bug in If,Online when running from command line
fixed - EmbeddedWB bug by using newer package
added - RegWrite 0x3 accepts one %Variable% as input value

Release as 078 SP3 on 2009-NOV-01

• They appear only on very few situations
• The changes are coded in just some lines

• Pedrole15's 'Long line' issue
• Galapo's Set,%var%,NIL,PERMANENT issue

[078 SP2]
date=2009-09-06

changed - separate TNodeData unit with 'read on demand'
added - Download center now can select by Version, MD5, Certification
fixed - RegWrite multiple strings with comma in argument
fixed - Bug ID #217: Set,%var%,NIL,PERMANENT
fixed - Smaller issue with resolving nested variables
fixed - Bug ID #216: Access Violation when trying to trim empty string
reanimated - CheckListBox
added - change event to ComboBox
added - change event to RadioGroup
fixed - terrible bug with strFormat cutting long lines. Changed all according AnsMidStr Delphi commands to length of MaxInt

Release as 078 SP2 on 2009-SEP-24

Sorry don't get you're drift. Do you mean a group of WB coders?

At the time, EACH time, there was large amount of agreeing and nothing actually DONE in the right direction.

Let's see if this time something changes.



jaclaz

• In former times
  • Nuno collected the demand of users
  • Nuno translated the demand into code
  • Nuno Tested
  • Nuno decided when to deliver
• In the near past
  • psc collected the demand of users
  • psc translated the demand into code
  • psc tested
  • psc and Nuno decided when to deliver
• In the future
  • MedEvil collected the demand of users
  • psc translated the demand into code
  • Joshua tested
  • MedEvil decided when to deliver

• Consuming and accepting
• Consuming and asking
• Testing and accepting
• Testing and complaining

For me, I think I was by default declared as Beta-Tester.
As maintainer of Common_Api I think I should
Do I need ask for ?

Pedro

• faster startup and interface drawing by 'read on demand'
• redesign of the Ice-Age script engine (with hundreds of addons, workarounds, quotes and comma inconsistency, etc. built in)
• raw WIM processing

Yes downloadex does not work - reports an exception and then hangs. Has to be killed off from task manager.

But because there has been no remarkable interest, I put the project into hibernating.
If you now download and test it propably will crash or fail due to the changes made to updates.ini