View previous topic :: View next topic |
Author |
Message |
mforkner
Joined: 04 Aug 2004 Posts: 78
|
Posted: Fri Oct 29, 2004 10:47 am Post subject: TOOL BAR |
|
|
I downloaded the toolbar example, and modified it to simply be a launch pad for MS WORD | EXCEL | ACCESS
It works fine and launches my programs in the IDE, but dies upon loading after an .exe build is executed from the START->RUN command. I rebuilt it with a console window to see any errors, and there is one--> Error: Error on function input arguments.
This error does not appear in the IDE console however.
DOS windows are so fast I had to reload the fella around 50 times to really get the whole msg down ....the comical side of programming. I looked for a funtion to stop or delay the console from exiting, but couldn't find anything on one in HELP or in COMPONENT TRAY.
So, does the IDE handle some exception and errors that the OS doesn't? Also, would you like an email with the VPD?
Thanks,
Michael Forkner |
|
Back to top |
|
|
CodeMorphis
Joined: 02 Dec 2003 Posts: 252
|
Posted: Fri Oct 29, 2004 5:52 pm Post subject: |
|
|
As indicated in a response to your other related posting, the problem has to do with a regression error in 1.1.2, which is now being investigated.
There are indeed some extra programming protection mechanisms available in the IDE which are absent in the generated exectuable. However, in this particular case it is not a user error but an executable generation error.
An example of how Synopsis protects users in the IDE from normally fatal programming errors in traditional IDE's is the ability to safely terminate endless loops. In the final executable you are no longer in the development environment and so it is not possible to prevent such protective programming errors but the IDE helps you to avoid such programming errors in the first place.
The reason why you did not see any error messages while in the IDE is because it ran fine. Of course, in the executable there was an error so an appropriate error message was written to the DOS console window.
If you double click on the executable in the Windows explorer then the DOS window will open and close very fast as the program exits. You can also open a DOS box by clicking on Start and then "Run..." in the Windows toolbar. Type "cmd" in the entry area and a console window will appear. Then you can invoke the program from inside the console window and the window will not disappear after the program terminates, allowing you to read all error messages generated.
Thanks for your posting - we are looking into the problem. |
|
Back to top |
|
|
CodeMorphis
Joined: 02 Dec 2003 Posts: 252
|
Posted: Sat Oct 30, 2004 12:46 am Post subject: |
|
|
The problem has been corrected in Update 1.1.3 which has been issued to the user base. |
|
Back to top |
|
|
mforkner
Joined: 04 Aug 2004 Posts: 78
|
Posted: Sat Oct 30, 2004 8:36 am Post subject: |
|
|
Thank you for the detailed explaination. Very helpful and informative. |
|
Back to top |
|
|
|