In SX Microcontrollers, SX/B Compiler and SX-Key Tool, dkemppai wrote:

[quote="Guenther Daubach"]
Dan,

looks as if you are living in a "crashing environment" [img]/forums/emoticons/smile.gif[/img] . Nevertheless, you can expect better help if you'd specify which OS you run on the "stock standard toshiba laptop" - is it DOS, Win 3.1, Win 98, Win ME, Win NT, Win XP, or Win CEMENT? 

Don't know what Win CEMENT is ? Well this is said to be the latest MS OS composed of all the bugs found in Win CE, Win ME, and Win NT.

Concerning changing my code, I'm always open for suggestions. Well, I'm using VB but I'm sorry - I don't understand why you are asking for a change. Why should I display the Common Dialog Open/Save windows w/o actually using the control. To my knowledge, I'm using this dialog only when the "Load File" button is clicked, and in this case, I'll need to allow the user to select the list file to be loaded. So why should I display this dialog w/o actually using this control. Could you please be a bit more specific - thanks.

[/quote]
 

[b]Guenther, [/b]

I tend to be really good at finding software bugs. I should really be a beta tester. As for the computers, I'm using winXP on every machine that the software is crashing on. XP pro on two of them and XP home on the laptop. 

As for the Control/Class. SX-Sim loads the control with the exe itself. (Actually, due to apartment model programming, it loads a copy of the workspace used by the control, but this is a minor detail). If you used the control as most people do, it exists on a form (probably the main form). It is loaded when the form is loaded. Even though the you only "use" the control when "Load File" is clicked, it is actually loaded as soon as SX-Sim starts. 

This is the reason that I am having the trouble. 

 

The Comdlg32.ocx is just a chunk of code that makes API calls in windows and tells windows to display all of the dialog boxes. Thes dialog boxes are already built into windows. The Comdlg32.ocx is just a wrapper to make it a little easier to access the API calls. The API's are actually what do the work, and display the dialogs. In the case of the code example that I posted the link to, someone rewrote the functions in the .ocx and put them in a .cls file. The comdlg32.ocx can be replaced by the object class, which whill then be compiled into the VB program. That object class functions exactly the same as the control, however the control is never called/loaded.  The program (in this case SX-Sim) would never access the Comdlg32.ocx control (It would never need to). Any version compatability issues with Comdlg32.ocx would go away (that I'm aware of!).

 

This issue really arrises when you distribute only the *.exe file. The SX-Sim program is not really a stand alone program, yet it is distributed as one. Most programmers would consider this to be poor programming practice (Please don't take offense at this, I am not diminishing the work you put into it. SX-Sim is a very nice program). Since SX-Sim has dependencies on other controls, removing the dependencies would truly make it a stand alone program.

 

Does this make sense? 

 

-Dan

 

FYI, Ever wonder why the comdlg32.ocx displays different dialogs depending on the OS? That's because the OS actually has the dialogs, and the control just calls them up.

---------- End of Message ----------


You can view the post on-line at:
http://forums.parallax.com/forums/default.aspx?f=7&p=1&m=80628#m82487

Need assistance? Send an email to the Forum Administrator at forumadmin@parallax.com

The Parallax Forums are powered by dotNetBB Forums, copyright 2002-2005 (http://www.dotNetBB.com)