Hi Guys,
No new BETA this weekend, but I have gone through all the posts since my last one and can confirm the issues I reproduced and fed back on the ones that either could not or for one reason did not apply to U75. Thanks for your time in bashing this interface into shape, I think we are getting there, just a few more niggles to iron out.
Confirmed:
1. When you press F1 to get context sensitive help, and the help page is already open, the interface should switch to the help page tab automatically.
2. Make the failure to save a .BAK file silent (so manually created folders do not trick the error)
3. Make sure if the user selects SAVE PROJECT AS into the same folder and project name as the current project folder and name, simply treat SAVE AS as a simple SAVE to avoid the 'transfer error message'
4. Only prompt the 'would you like to move these files' if there was a project that contained media files, as it is confusing to offer this choice when there are no files to transfer
5. When you start a new DBP session, and type some code, then instantly go to FILE > SAVE AS you are deposited in the Windows Temp folder instead of the DBP Projects folder
6. Prevent the SAVE PROJECT and SAVE PROJECT AS from accepting a .DBA file extension as this confuses end users. Automatically change any use of DBA with DBPRO file extension to ensure correct file usage
7. Ensure the new interface detects the difference between SYNC ON : and SYNC ON: (and related instances) so that ON: is not determined to be a label, and in fact the SYNC ON string supercedes label detection
8. Ensure the code auto-complete only adds end-code when cursor is at END of start code syntax (so placing cursor first !DO and then hitting return does not result in LOOPDO)
Feedback:
bloody bamboo : Cannot reproduce the debug and step through crash. Tried a simple program that increement the varaible A and it worked fine
pcRaider : The auto-code completion feature is not as powerful as you assume. Better that you switch this off in the Options menu to avoid further distraction
pcRaider & HowTo : The undo and redo features are available through the menu and keyboard shortcuts, we removed them from the toolbar to clean up the interface and make room for the store and module viewer
pcRaider : There are no plans to add International Character support to the new interface
Enter the Cypher : The code you provided compiled and parsed fine into the DBP debugger (F6) so I could not reproduce the crash you reported. Try BETA5 when it is released as we may have updated the build.
mrHandy : We are not fixing the old editor, this beta is focusing on the new interface. Perhaps I misunderstood the meaning of your post?
xGEKKOx : We are not adding any features for the next few updates, this is a route bug fixing session focusing on the new interface (which replaces the old editor from this version onwards)
MasterBowyer : This beta is to test the stability and functionality of the new U75 interface. If a bug exists in U74 relating to the compiler, we will look closer at this during the U76 beta.
Green Gandalf : Opening DBP will open into a blank workspace with no project. By selecting ADD TO PROJECT without having a project means the DBA is just created in the PROJECT root folder. The reason the BAK file could not be created is that at the moment you selected save, the folder did not exist, only at the point of saving (after you manually created the folder) did it exist, and of course by that time you are too late to make a copy to the .BAK file. If you saved again after the error prompt, it would have saved the .BAK file for you. I will make the BAK file error silent so it does not annoy. Also your point on the issue of resaving your project file into the same directory will be solved. If when you say 'open a dba' in your initial post you mean open an existing DBA (rather that it's project file), then disregard much of the above sequence. I have put the 'transfer error' message as a confirmed bug to fix as I can see how it might be confusing.
Green Gandalf : To start a prject cleanly, I often open DBP and then go to FILE > NEW > PROJECT, then enter a meaningful name then click OK. This creates for me the DBA, the DBPRO file, the project folder and removes the untitled.dba from the blank workspace. As I often do it this way, I have missed the strange errors you get when you create a project in other ways
Green Gandalf : I cannot reproduce the bug which ran the old version of your code when you made a change to the untitled.dba. Can you produce a step by step from opening DBP to seeing this behaviour, thanks.
Green Gandalf : Thanks for your continued patience, it might seem like a long and horrible road but it will be worth it and many of Johns fixes are now part of this new interface. Looks like I forgot the one about the SAVE AS opening up in the TEMP folder, will sort for the next beta (see confirmed above)
HowDo : U75 beta is intended to sort out the new interface issues. Compiler and command issues will be looked at with U76.
I have an internal BETA5 bubbling away here, but I want to perform a full rebuild of all the modules and fix those confirmed issues above before I subject you to another update. Hopefully you can see the sense in focusing on the interface to the exclusion of compiler and command considerations. There is no sense having a decent compiler and command set if the interface then decides to eat your code. If I can get responses to my feedback as well, I might also squeeze in those additional fixes if I can reproduce the problems.
I drink tea, and in my spare time I write software.