ODF creation - Linking [General001] in ODF to Setter panel #2109
Replies: 11 comments 1 reply
-
You're defining ODF generals with this entry. They are not the same as the Panels->Generals generals. ODF defined generals are "old style". Instead you're encouraged to use the built-in generals of GO.
Yes. Use this on any panel you wish to display it on: [Panel999Element999] Note that the [Organ] NumberOfGenerals will be set to 0 in such cases since you're actually using the GO built-in versions instead. I think that in https://www.youtube.com/watch?v=nitHpBEDsFI&list=PLNz9AJhjubTdw0pV2nZC_XfphJhJV5ly3&index=6 I cover most of this issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a bunch, Lars. This seems to be exactly what I was looking for. I removed all generals and instead added [Element001] [Panel001Element001] [Panel002Element001] but GrandOrgue denies to use them. I presume I have to add something like NumberOf[Gui/U|]Elements=1 to the organ section, but this didn't do the trick. Any idea? ODF is attached as a reference. |
Beta Was this translation helpful? Give feedback.
-
|
[Element001] is an unvalid section name. You should have for example : and in the [Panel001] section (not in the [Organ] section) to set NumberOfGUIElements= the number of Panel001Element999 sections. |
Beta Was this translation helpful? Give feedback.
-
|
So I tried: [Panel001] [Panel001Element001] The same in panel002l Result: Dienstag, 04. Februar 2025 um 22:31:39: 22:31:39: Warning: Nicht verwendeter ODF Eintrag 'Panel002Element001/ImageOff' Can this be caused by other GUI elements, such as NumberOfSetterElements=2 [Panel001SetterElement001] [Panel001SetterElement002] or NumberOfSwitches=48 ? |
Beta Was this translation helpful? Give feedback.
-
|
Try with NumberOfGUIElements instead of NumberOfGuiElements |
Beta Was this translation helpful? Give feedback.
-
|
[Panel001SetterElement001] [Panel001SetterElement002] are old panel format definitions, they can be replaced by the new panel format syntax : [Panel001Element001] [Panel001Element002] With the new panel format, all visual elements can be defined with Panel999Element999 (with the proper Type defined) and Panel999Image999 sections. |
Beta Was this translation helpful? Give feedback.
-
|
I highly advocate using tools like OdfEdit and/or GoOdf instead of manually editing the .organ files. Too many mistakes are likely to creep in! |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, thanks a bunch for all the help. I thought I was almost done with the ODF, but obviously there's a ton of things I still need to learn. Will investigate further during the weekend. |
Beta Was this translation helpful? Give feedback.
-
|
@larspalo Thanks for the suggestion. Unfortunately I experience several issues when using GOOdf, e.g.:
|
Beta Was this translation helpful? Give feedback.
-
|
Dear all, thanks to your help I was able to accomplish the mission :) . I opened my ODf with GoOdf, fixed resulting issues manually and got converted my old style objects to GUI elements. I was then able to convert the old style generals to new style generals, and now the user interface behaves as expected. Thanks a bunch, @larspalo and @eturpault |
Beta Was this translation helpful? Give feedback.
-
|
@Christedge Thanks for your efforts. The first issue you mention was just because you needed a more recent version of GO for the ODF created with GoOdf to be compatible. The specification/requirements of the ODF have changed over time and now (as mentioned in the GoOdf repository readme) the version of GoOdf and GO needs to be "in sync" for everything to work as expected. Anyway, great that you got it to work! |
Beta Was this translation helpful? Give feedback.
-
|
Oooops. This is it. I kept GO up to date on the machine which is connected to my console, but I completely missed to keep it up to date on my desktop, where I do the development work. Now GO opens files created with GoOdf without any issues. I apologize for the traffic. |
Beta Was this translation helpful? Give feedback.
-
Dear all,
I'm quite new to VPOs so bear with me in case I oversee the obvious. I currently try to write an GO-ODF for the famous Weissenau Hauptwerk sample set. It features some setter controls directly in itss panels, so I also placed some setter buttons directly in two of my panels.
Everything works fine so far. However, I expected "my" buttons to correspond with the setter panel, but it doesn't. Both seem to act independently. So my question is whether it was possible to address the setter panel buttons from the ODF. Currently I have:
[General001]
Name=
Displayed=N
Protected=N
NumberOfStops=0
NumberOfCouplers=0
NumberOfTremulants=0
NumberOfDivisionalCouplers=0
NumberOfSwitches=0
[General002]
…
[Panel001General001]
PositionX=1663
PositionY=28
ImageOn=000460\pics\cockpit\on\generals_01.png
ImageOff=000460\pics\cockpit\off\generals_01.png
[Panel001General002]
…
[Panel002General001]
PositionX=95
PositionY=1018
ImageOn=000460\pics\cockpit\on\generals_01.png
ImageOff=000460\pics\cockpit\off\generals_01.png
[Panel002General002]
…
Are there any other ODF elements I should use instead?
Thanks a bunch,
ce
Beta Was this translation helpful? Give feedback.
All reactions