The IF_EVAL bug has been solved maintaining backwards compatibility.

[the bigg]

See the, um, topic title   

All diffs are available from http://bigg.spellholdstudios.net/weidu_diffs, and contain all my diffs from a previous thread, plus the NO_IF_EVAL_BUG tp2 action and some reformatting of a couple of install-time strings (namely, if the mod has more than 4 components, there is no ASK_EVERY_COMPONENT etc, the installer will now display the name of the tp2 file; moreover, you can now nstall one component, not only [Y]es it. This can make it easier to tailor eventual custom tra files (EG @-1006= "Install Component [") can now be expressed as @-1006 = "What do you want to do with component [", or similar.

If you want the compiled executable PM me (according to the GPL under which WeiDU is released, I can distribute it, provided I make it clear that the file was modified by me and list the date of each change, but before embarking in an 'official' role I prefer to bone up on Ocaml a bit more). Don't use this executable for distributing your mods just yet, though!

[Borsook]

Does this mean that Weimer is gone for good?

[the bigg]

I haven't talked to him yet (one of the main reasons why I didn't give a link to a version with these diffs) and I hope not, however I'm sure you noticed a rather... long hiatus.

[Borsook]

I haven't talked to him yet (one of the main reasons why I didn't give a link to a version with these diffs) and I hope not, however I'm sure you noticed a rather... long hiatus.

Yeah, I noticed, that's why I'm asking...

[Loriel]

Regarding the long hiatus:  It was my impression that weimer has a once-a-year long hiatus because of other responsibilities and to regain some semblance of sanity.   Is this hiatus different than previous years?

EDIT: spelling

[Andyr]

I don't know if he has finished his doctorate yet, but if not it is highly possible that his end-of-year (or end-of-doctorate) examinations and meetings could be going on around this time of year.

[the bigg]

I don't know if he has finished his doctorate yet, but if not it is highly possible that his end-of-year (or end-of-doctorate) examinations and meetings could be going on around this time of year.

Well, this'd explain it all 
at least he has lots of diffs to apply when he gets back 

Also, new addition: the BACKUP directory is created if missing; thanks to this, MKDIR ~a/b/c/d~ is now a shorter equivalent to
MKDIR ~a~
MKDIR ~a/b~
MKDIR ~a/b/c~
MKDIR ~a/b/c/d~

[Grim Squeaker]

Regarding the long hiatus:  It was my impression that weimer has a once-a-year long hiatus because of other responsibilities and to regain some semblance of sanity.   Is this hiatus different than previous years?

EDIT: spelling

As well as the point Andy made I'd imagine he's also gotta be busy working on WeiNGINE.

[the bigg]

CLI options --language X, --force-install X, --force-uninstall X, --force-install-rest X Y..., --force-uninstall-rest X Y... are added, to allow easier making of scripts to replicate an install (soon to follow).

SET_THE_INTERACTIVE_VARIABLE tp2 action added; the tp2 variable %INTERACTIVE% allows to track wether the install session is interactive or not (to emulate AT_NOT_INTERACTIVE_EXIT or whatever).

diffs, as usual, are available from here: http://bigg.spellholdstudios.net/weidu_diffs.

[the bigg]

- Bugfix to --force-install X resulting in infinite loop if the mod component fails to install.
- REQUIRE_FILE, FORBID_FILE and FILE_EXIST behave as before, except that, if they are fed a bif file, they search it inside the key (so that this works also with multiple installs).

Diffs are available from the same place as the previous posts 

May one (or more) Mac users contact me for running a compatibility test for this (rater tricky) diff?

[Borsook]

The Clis look very handy. Are the changes being tested (I mean by others then yourself) and will you be releasing 186, or will you wait for Weimer?

[the bigg]

Heh, I know they're useful - I just built my game yesterday   

However, before releasing I'll ask Weimer (which I haven't done) and try to learn Ocaml a bit more 

Also, they aren't tested with SUBCOMPONENTS... :/

[Borsook]

Also, they aren't tested with SUBCOMPONENTS... :/

BTW SUBCOMPONENTS work not so well with install all option, i.e. the first component is installed, can something be done about it?

[the bigg]

Also, they aren't tested with SUBCOMPONENTS... :/

BTW SUBCOMPONENTS work not so well with install all option, i.e. the first component is installed, can something be done about it?

Err, how would you propose to change --yes with subcomponents?

BTW, in refinements components 20 and 21 are both part of the same subcomponent group.
setup-refinements --force-install-rest 21 20
and
setup-refinements --force-install-rest 20 21
will install 20, not 21;
setup-refinements --force-install 10 --force-uninstall 10
is not defined (IE don't do that).


EDIT: Seeming unrelated: ADD_KIT/PRO/MUS has better detection routines (EG you can add swashtF if sswashtF is already present as a kit) and will set the variable even if the kit is already present (ADD_KIT ~TRUECLASS~ parameter_list will still set ~%TRUECLASS%~ to 0)

[Borsook]

Also, they aren't tested with SUBCOMPONENTS... :/

BTW SUBCOMPONENTS work not so well with install all option, i.e. the first component is installed, can something be done about it?

Err, how would you propose to change --yes with subcomponents?

BTW, in refinements components 20 and 21 are both part of the same subcomponent group.
setup-refinements --force-install-rest 21 20
and
setup-refinements --force-install-rest 20 21
will install 20, not 21;
setup-refinements --force-install 10 --force-uninstall 10
is not defined (IE don't do that).

I rather meant the default option given to user "ask about each, install etc" if one has e.g. 20 components and only one with subcomponenst it's still necessery to use ASK_EVERY_COMPONENT lest should the player choose "install all" and get subcomponent one. I'd propose that the said install all ignored all components with subcomponents.

EDIT>typo... though it was a funny one and maybe should have been preserved...

[the bigg]

Also, they aren't tested with SUBCOMPONENTS... :/

BTW SUBCOMPONENTS work not so well with install all option, i.e. the first component is installed, can something be done about it?

Err, how would you propose to change --yes with subcomponents?

BTW, in refinements components 20 and 21 are both part of the same subcomponent group.
setup-refinements --force-install-rest 21 20
and
setup-refinements --force-install-rest 20 21
will install 20, not 21;
setup-refinements --force-install 10 --force-uninstall 10
is not defined (IE don't do that).

I rather meant the default option given to user "ask about each, install etc" if one has e.g. 20 components and only one with subcomponenst it still necessery to use ASK_EVERY_COMPONENT lest should the player choose "install all" and get subcomponent one. I'd propose that the said install all ignored all compomponents with subcomponents.

I can't see wether this is possible or not and wether this is a good idea or not (for example in Refinements you get a subcomponent choice for the language for the armor revision part, and then install armor revisions, so you won't get updated descriptions this way).

[Borsook]

Also, they aren't tested with SUBCOMPONENTS... :/

BTW SUBCOMPONENTS work not so well with install all option, i.e. the first component is installed, can something be done about it?

Err, how would you propose to change --yes with subcomponents?

BTW, in refinements components 20 and 21 are both part of the same subcomponent group.
setup-refinements --force-install-rest 21 20
and
setup-refinements --force-install-rest 20 21
will install 20, not 21;
setup-refinements --force-install 10 --force-uninstall 10
is not defined (IE don't do that).

I rather meant the default option given to user "ask about each, install etc" if one has e.g. 20 components and only one with subcomponenst it still necessery to use ASK_EVERY_COMPONENT lest should the player choose "install all" and get subcomponent one. I'd propose that the said install all ignored all compomponents with subcomponents.

I can't see wether this is possible or not and wether this is a good idea or not (for example in Refinements you get a subcomponent choice for the language for the armor revision part, and then install armor revisions, so you won't get updated descriptions this way).

Maybe I wasn't clear, I meant that even if the user does not want to be asked about each com and install all he should still be asked about those with subcomponents. In current situation either modder uses ASK_EVERY_COMPONENT and user has to answer Yes 20 times or the modder doesn't use it, user chooses install all and never knows there was a choice to be made.

[the bigg]

Maybe I wasn't clear, I meant that even if the user does not want to be asked about each com and install all he should still be asked about those with subcomponents. In current situation either modder uses ASK_EVERY_COMPONENT and user has to answer Yes 20 times or the modder doesn't use it, user chooses install all and never knows there was a choice to be made.

Ah, OK - after I'm done ironing out a couple of bugs/features from ADD_KIT/MUS/PRO 

[Borsook]

Maybe I wasn't clear, I meant that even if the user does not want to be asked about each com and install all he should still be asked about those with subcomponents. In current situation either modder uses ASK_EVERY_COMPONENT and user has to answer Yes 20 times or the modder doesn't use it, user chooses install all and never knows there was a choice to be made.

Ah, OK - after I'm done ironing out a couple of bugs/features from ADD_KIT/MUS/PRO 

Great.

[the bigg]

Diffs (and executable for those who know the link) have just been updated with the aforementioned ADD_KIT fixes (I didn't touch the discussed issue with subcomponents).

[Borsook]

Diffs (and executable for those who know the link) have just been updated with the aforementioned ADD_KIT fixes (I didn't touch the discussed issue with subcomponents).

You work fast! Hmm and where pray is the thumbs up icon? Oh, well, think back to PnP and visualize

[the bigg]

Nah, this was all the diff (as in diff -p -b -E):

Code: [Select]

*** 2837,2849 ****
          (PE_And(
          (Pred_File_Exists(PE_LiteralString "override/kitlist.2da")),
          (Pred_File_Contains(PE_LiteralString "override/kitlist.2da",
!           PE_LiteralString k.kit_name))))) then begin
          log_and_print "\n\nERROR: Kit [%s] already present! Skipping!\n\n"
          k.kit_name
        end else begin
--- 2904,2916 ----
          (PE_And(
          (Pred_File_Exists(PE_LiteralString "override/kitlist.2da")),
          (Pred_File_Contains(PE_LiteralString "override/kitlist.2da",
!           PE_LiteralString ("^" ^ k.kit_name ^ "\\b")))))) then begin
!         Var.set_int32 (k.kit_name) (Bcs.int_of_sym game "KITLIST.2DA" k.kit_name) ;
          log_and_print "\n\nERROR: Kit [%s] already present! Skipping!\n\n"
          k.kit_name
        end else begin


[the bigg]

Slight fix to the cli options. Updated fix and executable.

[the bigg]

Maybe I wasn't clear, I meant that even if the user does not want to be asked about each com and install all he should still be asked about those with subcomponents. In current situation either modder uses ASK_EVERY_COMPONENT and user has to answer Yes 20 times or the modder doesn't use it, user chooses install all and never knows there was a choice to be made.

...done 

[Borsook]

Maybe I wasn't clear, I meant that even if the user does not want to be asked about each com and install all he should still be asked about those with subcomponents. In current situation either modder uses ASK_EVERY_COMPONENT and user has to answer Yes 20 times or the modder doesn't use it, user chooses install all and never knows there was a choice to be made.

...done 

Wow. Can I use it for distribution, can I? can I?