Sticky folder

[Sergio_S]

I am trying to use a sticky folder in the Select Install Folder screen. I have been using a code that was once presented by Brett in the thread:
http://www.indigorose.com/forums/sho...ghlight=sticky

It works fine sticking the folder when selecting a new location through the Browse button (the control message is from the browse button), but does not avoid the user to change it through typing a new location (the control message is from the install folder field).

I want to allow the user either to select or to type a different path without change the application folder. I have been trying to write a similar code when typing the new location unsuccessfully.

Any idea??

[Adam]

Sorry but I still don't fully understand your question. Add a little detail and I'm sure that we'll figure this out

Adam Kapilik

[Sergio_S]

Adam,

What I mean is to set in the project an install folder which will be allways at the end of the install path whatever that path could be. For instance, I can set as default a install path like C:\program_files\my_project, where the folder my_project is my sticky folder. The user then could change the path from the suggested default to any other, for example, to C:\program_files\special_software\my_project. The folder my_project remains stuck to the end of the new path.

The change in the path can be done either through the browse button or by typing the new path in the field . The mentioned link in my former post has an example of how to achieve this by actuating in the control message fired from the browse button. The problem is, how to do that if the user decides to type in the field.

I hope this may clear the point.

Note: This is intended to be done in the Select Install Folder screen.

[Adam]

Sergio,

Use the method in This knowledgebase article instead. It uses the "On Next" event so it should not matter if the user types the path or browses for it.

Adam Kapilik

[Sergio_S]

Adam,

Thank you for your help.
In fact, the method described in the article worked as a workaround, but why not to include this feature in SUF 7 as a built in feature as it was in SUF 5 and made it as simple as it used to be?
My contribution to the SUF 7 suggestion box.

[Adam]

Thanks for the suggestion.

Adam Kapilik