Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have to this for my software as I need to support many different types of motion controllers for metal cutting machines.</p> <p>Your interface has the basics you need. The thing you need to remember is that you don't need to pass in a list of parameters. You pointed out each type of device could have a very different type of setup. </p> <p>The way I do it is as follows</p> <pre><code>interface IMeasurementInterface { void Initialize(); void Close(); void Setup(); void Read (FileReader as &lt;whatever read file object you are using&gt;) void Store (FileReader as &lt;whatever read file object you are using&gt;) string Name(); } </code></pre> <p>Setup calls a dialog box created in the assembly of the IMeasurementDevice. The dialog is NOT Visible outside of the assembly.</p> <p>Now I know some object oriented or MVC purist may object to this. However I feel the concept of hiding the internals of a specific Measurement class outweighs strict adherence to the MVC architecture. </p> <p>My general philosophy is that trival dialog are implemented in the same assembly provided that it is private to the assembly and called by an object implementing on the standard interfaces that I setup. Again the reason for this is I find hiding the internals to be more valuable than trying to implement all the dialogs in the top level assembly. </p> <p>By specifying a Read Method and a Store method you eliminate the need to expose the internal setup parameters for saving. All you need is to pass whatever type of file storage object you are using to save your setup parameters.</p> <p>Finally like another poster stated you need to setup a Factory Class in your assembly containing all your measurement devices. During your setup you need to instantiate this class and retrieve the list of supported measurement devices. </p> <p>The way I do it is my factory class retrieves a list of motion controllers. This list is part of a master class where all the setup classes are stored. When I read my setup files I get the controllers that are actually being used. I retrieve those classes out of the list and place them in another list that is actually used during the cutting process.</p> <p>The reason I do it this way is that when the user is setting up motion controllers he need to be able to pick from a list of ALL the available controls in order to tell the software which one he has. I find it more responsive to keep a list of available controllers around.</p>
    singulars
    1. This table or related slice is empty.
    1. PODefine an interface method that takes different parameters
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USRS Conley
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThis could work, however I need to pass some configuration parameters from the UI, without opening a dialog. If I only want to change the number of points to measure I want to do that from the main UI and not from a setup dialog. Therefore I wanted the Setup to accept parameters
      singulars
      1. PO
      1. USEnrico
    2. COIn our software we have Shop Standards which are accessible from anywhere in the software. I recommend putting that parameter (and others like it) in your version of the Shop Standards.
      singulars
      1. PO
      1. USRS Conley
    3. COWhich parameter goes where I use the rule of 1) If it pertains to ALL devices of the same class. Put in the Global Shop Standards. 2) If it is specific to the device hide it behind the device interface. In other case you don't need to pass extra parameters through setup.
      singulars
      1. PO
      1. USRS Conley
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload