About MarvinW

Hello, OES 4.11b user here. I am developing an object which has a structure that will most likely go into station data, which is often stored as a dat file. For the initial creation of the dat file I want to provide sensible initial values, which are sometimes not the default initial values of the data types. I found that the initialValue attribute does not seem to work on structure members that use enumRef. Using the .osd in OES seems to discard this information. Here is what I want to do: <Item name="CurveValue" enumRef="ATMOxAnalogInputArrayCurveValueEnum" initialValue="3"> <Properties> <Property name="Label"> <Text lcid="1033" value="Which value to display on the chart" /> </Property> <Property name="SelectEnumItems" value="True" /> </Properties> </Item> The initialValue seems to have no effect in OES, it is ignored. Apparently it's not possible to set initialValues for enums from .osd files at all, because I haven't found any that works. I can set it in the normal types definition in OES though, and when I activate "export STD files" the output also looks like my handwritten .osd above, but it doesn't work. Is there any plan to allow this feature in the future? For now my solution is to change the order of the enum items so my desired default coincides with index 0. If I needed different defaults for the same enum type in different places, then that would fail though. ... View more

Hello, I found 2 behaviors in OES v4.11b that I consider to be bugs. I created an object of type A and I found out that some parameters cannot be configured or do get lost when I reload STD. First of all, here is one such parameters: <ParameterVariable name="rInput" hierarchy="Input" refId="ATMOxPID_rInput" varType="LREAL" textEn ="bla bla." textDe="bla bla." subtreeInstanceSpecific="True" /> Now I have an object a. I cannot link object a's parameter to variables of object a's unit. I can select them in OES, but after I do the parameter is cleared again. I can link object a's parameter to the variables of object b's unit though, where object b is also of the same object type. But if I do that, then after reload STD the object parameter will be lost. If I link it to any other variable it seems to work fine. I think the problem is with the object's unit definition, which looks like this: <Unit refLink="A668CDB5-B088-4BC6-A09E-8151E9F1126A"> <Condition comparator="EqualTo" value="True" refLink="ATMOxPID_ExportFb"/> </Unit> <Unit refLink="7558CD31-B708-46CF-BB35-2426AC69D054"> <Condition comparator="EqualTo" value="False" refLink="ATMOxPID_ExportFb"/> </Unit> I guess when I reload STD it fails to recognize which of the two units I am using at the moment it is reloading the parameters, so it thinks the variable stopped existing. But why it immediately deletes my parameter selection if I select my own unit, I don't understand at all. Anyway, do you think this will be fixed in the future? Or do you have some more insight into this problem? Thanks. ... View more