Point 1 & 2 again enabling Splash Screen does it.
<i><font color="#663300"><i><font color="#663300">1) I am not able to reproduce again this but just for reference. When the app starts the Edit and Windows menu pad is enabled but if I press Alt to open any the pad they are disabled.</font></i>
I don't know why that happens. I guess something needs to force the menus to update their status. If you can figure that out, let me know.
<i><font color="#663300">2) I am not able to reproduce again this but just for reference. Why is the Format pad there after the Help pad. It seems to want to stay back from the development environment.</font></i>
Again, I don't know. I haven't played with class-based menus in quite some time.
<i><font color="#663300">3) The following line is still missing from a new newapp in aDataEnv.PRG
*-- SECURITY
DEFINE CLASS SECURITYEnvironment AS iDataEnvironment
cDefaultDatabaseName = "SECURITY"
*** this line is required for security to function
cDefaultViewDatabaseName = "SECURITY"
cDefaultLocalLocation = SYS(5) + SYS(2003) + "SECURITY"
cDefaultRemoteLocation = SYS(5) + SYS(2003) + "SECURITYREMOTE"
ENDDEFINE</font></i>
Security is not supported in 6.2. If you want to use it, you have to add it yourself. I'm hoping that once we can get the source up in a CVS environment, those of you who use the security features can work out a methodology for implementing security without dragging along all the rest of the SAVI baggage.
<i><font color="#663300">4) A suggestion: When the toolbar is in New or Edited record mode disable the navigation buttons completely, in fact only Save, Revert and Exit buttons to be allowed. So that the user knows what are his expected behaviours.</font></i>
Codebook is not designed to be a modal environment. They can always edit, and if they try to navigate without committing their changes, they are asked to save. If you want to make something modal, you should use a modal form, and not try to make the standard toolbar behavior fit it. Instead, create your own toolbar to support modal operations.
<i><font color="#663300">5) A suggestion (again 8-)): When only one record is in the table then navigation is essentially useless thus disable the navigation bar when only one record is present. Trust me, I know of users (not everybody is lucky you see) who will phone me saying that he has entered one record and he is trying to navigate and the buttons are, but the form is not responding to his navigation.</font></i>
OK, I can see where a single record still permits navigation. I've changed it for the next release.
</font></i>
Regards
Bhavbhuti
©2002 Bhavbhuti Nathwani |
