17 replies to this topic

[PaPeuser]

Wishlist Wish
I wish Winbuilder Would\Could create different .ini files based on source used.

[pscEx]

A reasonable request!

I'll try.

But it is not so easy.

Currently WB reaads WinBuilder.ini on start. That has to be moved to a 'logical place after project selection'.

Maybe that brings some troubles.

I'll see what can be done.

Peter

[Lancelot]

you can use different winbuilder names

winbuilder077RC2_projectA.exe
winbuilder078SP6_projectB.exe

check the .ini file they produce

[PaPeuser]

@Lancelot
I have 7 different build folders now.
More if I count Bart and XPE builds
Since Vista and Win7 can be built in Multi Win7 it would be nice to put them in same folder.
But I do not remember what works with what, what needs unchecked or checked,,
New users most likely only use 1 maybe 2 build folders.

This helps with testing scripts

[Lancelot]

@Lancelot
I have 7 different build folders now.

hehe, only 7, I have 10 folders only for nativeex

Since Vista and Win7 can be built in Multi Win7 it would be nice to put them in same folder.

This should be working.
Theorically, you can use some of active projects with single winbuilder (use wb078sp6)
As far as I know (remember), List is:

LiveXP
nativeex_barabone
nativeex_Win7Rescue
VistaPE-CAPI
Win7Rescue
Win7PE

All with single winbuilder

please test

[PaPeuser]

Since i limit my testing right now to Multi Win7

Projects can be ok,, but i have a problem going from 32 to 64

[Lancelot]

Projects can be ok,, but i have a problem going from 32 to 64

what is the problem !!!
when you change your source, if project support new source than okey !!!!

what is the releation of the problem with winbuilder (or and winbuilder.ini) !?!?!

[MedEvil]

@PaPeuser
Are you sure about your wish?
Your wish and the goal you're trying to acomplish seem to be not related.




edit:
Maybe you were thinking about a script.project which switches with source?

[PaPeuser]

I think your right ,, its not the Winbuiler.ini file, I am nuts ,, Never mind ....................................................................

[Brito]

You'll need to be a bit more explicit.

Otherwise I'd suggest script.project as the ideal place for customizations tailored for a single project.

It wouldn't be a good idea to keep the base folder cluttered.

[PaPeuser]

Yes I was wrong,, script.project saves settings

When you change source in same project script.project gets over written

So to save setting with a 32 build and switch to a 64 build, you must reselect some scripts,

I will live the way it is,,, sorry for any confusion

Or is it project.ini?????????????????????/

[Lancelot]

So to save setting with a 32 build and switch to a 64 build, you must reselect some scripts,

This is about project design, we preferred another way thinking the annoying "reselect" thingy, check here (post45 post46 and post47 4) )

[PaPeuser]

So this is not fixed yet???

I am not sold on it being a project fix

Sources are selected for project in Winbuilder and Winbuilder saved script selections for each project. Since Winbuilder saves all source selections (drop down source dir)

Why could it not generate a new saved selection based on each source?

[Lancelot]

So this is not fixed yet???

!!!! From my point of view there is no issue here to fix !!!???

Why could it not generate a new saved selection based on each source?

I do not understand, can you please explain giving example in details ????

[PaPeuser]

When the source directory is changed project tree selections should be refreshed to reflect selections that were made and saved with that source

[Lancelot]

When the source directory is changed project tree selections should be refreshed to reflect selections that were made and saved with that source

why ? as written on the relevant topic I pointed, When I change source I do not need to change any selection which does not cause trouble.
and as far as I remember, win7pe designed that way too (If not, it should be design problem)

But maybe, you are asking for an easy way to save your selections and restore them when you need ?

[MedEvil]

When the source directory is changed project tree selections should be refreshed to reflect selections that were made and saved with that source

If i understand you right, you want a certain set of scripts selected with 32bit source and a different set with 64bit source. Maybe even different setting within the scripts.

This is unfortunately not possible and a nuisance to me from the beginning. The settings of each script and if a script is selected or not, are stored inside the script and not an ini file, where they would belong imo.

btw. Peter. Would like to push an own wish too. Would it be possible to change the handling of WB, so that i can (un)selcet a folder, without the (un)selected state of the scripts in the folder being affected?
Would save a lot of time during testruns.

[Galapo]

This is unfortunately not possible and a nuisance to me from the beginning. The settings of each script and if a script is selected or not, are stored inside the script and not an ini file, where they would belong imo.

Using !WBManager.Script you can occomplish such a task. It stores all script delections and interface selections etc.

Regards,
Galapo.