it seams that the project path panel does no macro or variable expansion on the path (or Am I wrong)C::B version? Platform? What path panel (we have many)? Steps to reproduce?
txtPrjPath->SetName(_T("txtPrjPath")); // not such an original name :)This doesn't look good and I don't know what you are trying to "fix" with this.
C::B version? Platform? What path panel (we have many)? Steps to reproduce?Sorry should have known better :'( : Code::Blocks (svn 7671), Win7, Project Path Panel in New Project Wizard
This doesn't look good and I don't know what you are trying to "fix" with this.I need the Projects to be situated relative to the CB directory so if the text control holding the path has a "name" then I could expand the $(#cbtmp) variable in the script and create the project in a relative path and not absolute
C::B version? Platform? What path panel (we have many)? Steps to reproduce?Sorry should have known better :'( : Code::Blocks (svn 7671), Win7, Project Path Panel in New Project Wizard
This doesn't look good and I don't know what you are trying to "fix" with this.I need the Projects to be situated relative to the CB directory so if the text control holding the path has a "name" then I could expand the $(#cbtmp) variable in the script and create the project in a relative path and not absolute
I need the Projects to be situated relative to the CB directory so if the text control holding the path has a "name" then I could expand the $(#cbtmp) variable in the script and create the project in a relative path and not absoluteOk, understood. But then your patch doen't do the right thing and won't help.
You have to replace macros using macrosmanager but keep track of the original entry so the macro doesn't get lost.Thanks, I did think of doing it but decided against, let me explain me reasoning
// Set the control's name so that calls to wxWindow::FindWindowByName() succeed...
txtFolder->SetName(_T("txtFolder"));
so I tried minimal interventionIf what you tried works for you, I'm fine. I thought you want to make this generally available to all wizards.
[...]
what do you think is the right approach in this case
I thought you want to make this generally available to all wizards.I will be more then happy to do it if you think it might be useful,
can you point me at the coding standards document you are using or any other thing I should know?Here is for starters: