BenjaminKalytta

So I released first working pre beta. (Bug reports are welcome now) Following INI keys have been added: 1. collapsed.x=1|0 (initially collapse entire subtree) 2. selected=1|0 (selects section to be installed or not. Note, this is not selected.x which can be set individually per item (subtree)) This keyword can only be once per section! If Selected=0, none of the items in this section will be installed also if each of them would be checked! Following INI keys have been renamed: 1. hide.x will now be hidden.x INI file syntax doesn't changed any way except hidden.x Special behaviour: If you don't want a subtree/item to be an executable command but just a descriptive header key, set command.x=* In this case item texts will be bolded. Note also, if a tree is unchecked none of its subtrees/items will be executed. (This also applys to descriptive keys which contains one or more subitems) If a tree is hidden also each subtrees/items are invisible. EDIT: EDIT: Other question. Take this example: [ ] SUBTREE [ ] ITEM 1 [ ] ITEM 2 [ ] SUBTREE 1 [ ] ITEM 1.1 If SUBTREE is Checked/Unchecked, should this also check/uncheck entire subtrees like this: [x] SUBTREE [x] ITEM 1 [x] ITEM 2 [x] SUBTREE 1 [x] ITEM 1.1 Good night, it's late now Benjamin

This lead to the next question. At present each sub tree contain a command to be executed. Should I add an option where a subtree is just a subtree i.e. just for describing purpose? Benjamin

@Alanoll: didn't stop. how do you mean it didn't stop? @all: A general question. Example: There is this subtree: SECTION DESCRIPTION [x] SUBTREE 1 [x] SUBTREE 1.2 [x] ITEM 1 [ ] ITEM 2 [x] SUBTREE 2 ... What should happen if ITEM 1 is unselected? Should SUBTREE 1.2 also be unselcted? (hint: SUBTREE 1.2 is also A COMMAND!) or should this do nothing in SUBTREE 1.2? Benjamin

@midiboy: You can also do following: [environment] personal=%systemdrive%\%newusername%\eigene dateien my music=%personal%\eigene musik ... and so on. Benjamin

May be you are using and old version ... please redownload it bacause I've changed some things this day. Benjamin

EDIT: Everything is ok. That %NewUserName% will not be expanded is intended because this shellfolders will be used as global settings also for other users. Btw. your shellfolder settings works here ... every specified shellfoder will be displayed. Which WIHU switches do you use? Benjamin

Yes, that works, why don't you do it? You can set each shell folder in install.ini which will be used for each user (if not specified user specific shellfolders in users.ini) Benjamin

@midiboy: You are right. I fixed this 2 bugs. (Btw. /SkipSettings also skips user creation) No actually not. These folders will be created if users has been created which isn't the case at that time. So I can't read it out from registry because user profile folder and it's registry don't exists at this time. And I can't hardcode this paths because they are localization dependend. benjamin

@Osmosis Jones: I know this of course WAS a bug here, but please don't report ALPHA bugs ... only if released as BETA. Thx I changed my code so that each subtree can be hidden. Effect is that also it's subtrees are hidden also if this isn't specified in INI file. EDIT: But since root of the tree is only a description (section name) which don't contain command's to be executed should this be visible also if all of it's childs are hidden? Or should I hide it then (like in version WIHU 2.0)? benjamin

I think it should be visible. Take this example: [section 1]... [Creating users] command.0=createusers.exe blabla descritpion.0=will never be displayed hide.0=1 ...will be displayed at Section 1 ... Creating users EDIT: May be I shouldn't restrict hide.x to last level Benjamin

Yes this will be added this time. benjamin

EDIT: That's no problem as long as it isn't root tree ... in this case subtree will be treated as an Tree Item with no restriction. This could work: CD Burning Apps Nero ITEM 1 ITEM 2 Alcohol 2 Microsoft applications Microsoft Office 2003 Professional Image Viewer ACDSee IrfanView Benjamin

Ok, what about not allowing to hide a subtree, but only items on the last level of the tree? TREE SUBTREE 1 ITEM 1 ITEM 2 SUBTREE 2 In this example only ITEM 1 and ITEM 2 can be hidden but not SUBTREE 1 or 2. Benjamin

Im considered to remove hide.x key because it makes things unnecessaryly complicated. This was initially only added because of the miss of sub trees. What do you think about it? Or does anybody need this? Benjamin

At this time posting was made, alpha version 2.1 wasn't fixed yet (is also fixed now btw.) Both are fixed.Version 2.0 Alpha 2, Version 2.1 Sorry. Edit: I uploaded this file at 00:38 (GMT+1). Benjamin

As I said, it was fixed. Yes, I should update my web page Benjamin

Which click? I think I fixed all bugs now. Benjamin

No new version but 2nd alpha preview with install.ini with more than one level. (subcommands). It's only a preview, don't use this for software installation at this moment ... there are some things that have to be fixed first. (Should a "double click" expand/collapse a tree?) Alpha 2 can be found here Benjamin

Yes I don't uploaded fixed alpha yet. benjamin

I thinks it time to rewrite /autoinstall and /skip... things. Please test the new one. Thx for reporting this ... never give up benjamin

Im proudly present you the first alpha preview of version 2.1. INI file has not to be changed to work with this version. Sub items are expandable/collapsable. This version can be found here. I'll support up to 65535 levels of depth ... I think this is widely enough for you all For easyness I decided not to use XML, but retain INI instead. Benjamin Kalytta

Autoinstall will work as usual ... the only thing that changed is, that if user cancels autoinstallation i.e. pressing any key, pressing mouse and so on ... user has not to press Finish button on last screen i.e. wihu will exits automatically without waiting for user top press finish. (Note again: only if /AutoInstall is specified) Benjamin

Im so sorry for this 2 bugs ... fixed one and added 2 new ones No it should only restart if "Finish" is pressed. Also "Wait for Finish Press" bug is fixed. Application behaviour changed also: If specified /AutoInstall=<x> Wihu will never again wait for user to press "Finish" also if the user cancels auto install timer. Will this be ok? EDIT: problem is, Im currently developing version 2.1 with tree things ... so I always have to update 2 applications if I fix a bug in one benjamin

I think I know what you mean ... it should be already fixed. (Some day I'll remove Autoinstall and SkipXxx things if there are so many bugs inside. ) Benjamin

Yes it's a bug ... I think I should rename it back to beta 2 ... It's fixed now.(Btw. don't know why this din't work ... according to Windows API it should work as it was ... but as always documentation arent always perfect ) I don't kown ... seems to be just a return code from an application ... needn't say much. Benjamin