Trace:
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
visionx:faq_tech [2022/01/10 10:03] admin |
visionx:faq_tech [2022/08/08 09:34] admin |
||
|---|---|---|---|
| Line 110: | Line 110: | ||
| ==== Column with same name created when making a subtable ==== | ==== Column with same name created when making a subtable ==== | ||
| - | //When I click “Make Subtable” after adding a field on the “Edit table” screen, a mandatory column is added that has the same name as the subtable. This is always confusing to me, as I have almost never had a situation where I would have wanted to create a column that has the same name as the table. I am always unsure if best practice here would be to replace the table name with the intended first column name, or if the column with the table name has to be kept in place for another reason (especially since it is mandatory). Can it just be replaced? | + | //**When I click “Make Subtable” after adding a field on the “Edit table” screen, a mandatory column is added that has the same name as the subtable. This is always confusing to me, as I have almost never had a situation where I would have wanted to create a column that has the same name as the table. I am always unsure if best practice here would be to replace the table name with the intended first column name, or if the column with the table name has to be kept in place for another reason (especially since it is mandatory). Can it just be replaced? |
| \\ \\ | \\ \\ | ||
| - | Also, when I click the “Make Subtable” button in the “New Screen” wizard, the ID column is not shown. But when I edit an existing table, add a new field and click “Make Subtable” the ID column is shown. Is that intentional? // | + | Also, when I click the “Make Subtable” button in the “New Screen” wizard, the ID column is not shown. But when I edit an existing table, add a new field and click “Make Subtable” the ID column is shown. Is that intentional?** // |
| \\ \\ | \\ \\ | ||
| This is nearby best practice, the only downside is, that we do not know the plural or singular of the given word, to have it perfect. | This is nearby best practice, the only downside is, that we do not know the plural or singular of the given word, to have it perfect. | ||
| Line 143: | Line 143: | ||
| A table should have a name that describes the data it stores. | A table should have a name that describes the data it stores. | ||
| Normally this table should have a identifier/name column whose name describes which kind of data you get (so this should be the singular of table name), and whose value represents the whole row, to be able to use it as a combobox. | Normally this table should have a identifier/name column whose name describes which kind of data you get (so this should be the singular of table name), and whose value represents the whole row, to be able to use it as a combobox. | ||
| + | |||
| + | ==== Change E-Plug standard ports ==== | ||
| + | |||
| + | The standard ports for E-Plug communication are 1725 (E-Plug port in Eclipse for VisionX to E-Plug) and 1726 (Port in VisionX for E-Plug to VisionX). If you have problems e.g. ports are already in use, simply change the ports with following system parameters: | ||
| + | |||
| + | ''EPlugPort (default: 1725)''\\ | ||
| + | ''VisionXPort (default: 1726)'' | ||
| + | |||
| + | Simply add the system parameters to the [[#additional_jvm_start_parameters|start configuration of VisionX]]. | ||