Custom Query (116 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (58 - 60 of 116)

Ticket Resolution Summary Owner Reporter
#103 fixed Add attribute 'comment' to all objects ? ymipsl ssenesi
Description

For the sake of documenting xml files and their components, it would be helpful to be able to insert comment strings for every object, INSIDE the brackets enclosing the object. Maybe there is an XML syntax for that ? Otherwise, adding a 'comment' attribute would fit.

#104 wontfix When setting default field name, id should prevail on field_ref ymipsl ssenesi
Description

When writing :

<field id="oddust" field_ref="od550dust" ... />

Field "oddust" get the same name as field "odd550dust"

When writing

<field id="oddust" domain="dom1" >

field "oddust" has name=id="oddust"

I beliewe that most users expect that the latter behaviour applies in the first case

#111 fixed wrong consistency check in domaion.cpp on ni when data_dim=1 ymipsl ssenesi
Description

domain.cpp reads at line 730 :

      if ((ni.getValue() < 0 || ibegin.getValue() < 0) ||
         ((type_attr::unstructured != type) && ((ibegin.getValue() + ni.getValue()) > ni_glo.getValue())))

while it should be:

      if ((ni.getValue() < 0 || ibegin.getValue() < 0) ||
         ((data_dim.get(Value()== 2 && ((ibegin.getValue() + ni.getValue()) > ni_glo.getValue())))

as you can have data_dim=1 and e.g. type=curvilinear, which breaks the relationship between ni and ni_glo. Another formulation would be to use as a ceiling value for ni :

  • ni_glo if data_dim==2
  • ni_glo * nj_glo if data_dim==1
Note: See TracQuery for help on using queries.