1. I created a new folder, copied my project D10.fbz5 to it, and opened it in FB6. Then saved it, which wrote it as D10.fbz6. After this the main window title bar changed to show D10.fbz6, but the root of the tree on the Project tab remained shown as D10.fbz5. This fixed itself after shutting down and restarting FB6, but was confusing at the time.
2. I cannot find a way to prevent the program from starting with the Welcome page visible. I set 'AutoLoad Last Project' because I want to start working on the last project immediately after I start the program. Having the Welcome page always shown on startup simply wastes my time. However the 'last project' does load behind the Welcome page.
3. When I switch from the Welcome page to Design & Debug, the Quick Help tab at the bottom reads: "New Project. A new (blank) project has been created....". This is, of course untrue, because my 'last project' is visible above this message.
4. Path manipulation: the function "Remove File Extension" actually removes everything. In the log, the preceding list iterator shows the input variable as set to F7NDX.DLL, and the Path Manipulation as 'File extension removed' but the project workspace on the following command has empty strings inserted instead of F7NDX as expected. It is not possible to test much more of FB6 until I can get past this bug.
3. Can’t reproduce it. What action is selected when it’s happening?
4. Can’t reproduce - it worked as expected for me with “F7NDX.DLL”. Can you send me a short project file that shows the bug? (Also, put a Action.SendLogMessage() in the AfterAction of the Path Manipulation action to see what the value is immediately after the extension is removed).
3. It happens only when Show Welcome Page on Startup is checked, and when I have clicked on the Design & Debug tab to display the project. Now that I have unchecked the Show Welcome page (thanks for that info), I see a quick flash of the 'New blank project' Quick Help text as the program loads, then it switches to the correct quick help text when the project appears.
4. Not sure how to add an AfterAction, so I added a 'Log Variable Values' action after the Path Manipulation, which shows that the variable has been set correctly with the basename. What has actually failed is the expansion in the 'Build VC6/Embedded project', where the project folder name and .dsp name both use the basename variable. This appeared to work in FB5.
In FB6 I tried to check 'Expand variables in Project/Workspace file', thinking this might resolve the issue. However this simply caused an unhandled exception when the file was still not found as a result of the non-expansion of variables in the project filename. I will gather up the evidence and e-mail it to support.
I think the best solution for me is to unwind this list iterator and do the compilations individually. There are only 8 items in the list in this case.
3. works for me… does it happen with different project files?
4. I couldn’t reproduce this either, the variable expansion seems to work fine in the Build VC6 action for me. Can you send a test case to support please?