6.1     Creating rotation examples

The standard heat.pro example has been prepared for static analysis. The Food item is an element (visible on Select Element  list) and not an object (not visible on Select Object   list). Thus it cannot be rotated. We will delete it and define again with an elib/basic/cubo.udo script. An additional advantage of this approach is that the object will be parameterised, facilitating easy changes of its dimensions and positioning in the oven.

Fig. 6.1-1 Select Element list of the heat.pro example and Element Details dialogue of the Food element.

To note its original dimensions and position, we press the  button in 2D window and highlight Food on the list (left in Fig. 6.1-1). Pressing  shows Element Details as on the right of in Fig. 6.1‑1. We close this window with and then delete Food with .

Fig. 6.1-2 Dialogue for selecting UDO objects from libraries.

We now press  in 2D window and browse the directories to locale elib/basic. After highlighting it with a mouse, we see its contents as on the right of Fig. 6.1-2. The first one cubo is suitable for our project. Description explains that its origin is at the centre of the bottom. A single click over Description brings up the object dialogue. The settings in Fig. 6.1-3 reconstruct our Food item, which is now an object accessible via  command for modifications.

Fig. 6.1-3 Settings in cubo.udo dialogue which restore Food item.

Fig. 6.1-4 Project Info window indicating erroneous medium settings and UDO Editor showing the line with the erroneous parameter.

If QW-Editor encounters errors during UDO interpretation, it signals them to the user. Imagine that we have set medium to food instead of Food. The UDO language is case sensitive and medium food will not be found among the project media. QW Project Info shown on the left of Fig. 6.1-4 will pop up. Highlighting the Warning line and double-clicking over it opens UDO Editor with cubo.udo loaded into it, as on the right of Fig. 6.1-4. This feature is very helpful with detecting parameter mistakes or implementing new UDOs.