You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,10 @@ Creation of an usable odf for GrandOrgue with GOODF fully works, though it's pos
13
13
14
14
Note that the way to "save" the work done on an organ is by writing out the ODF (from file menu in the software or Ctrl+S), Save as is accomplished just by changing the organ definition file name. Since version 0.4 it's possible to also read/edit already existing .organ files. **However**, **be very mindful when using this feature!** It's possible that some bugs still exist that could potentially corrupt an ODF file. **Always work on copies or on files you don't mind having destroyed!** Also note that GOODF always will convert older type of .organ files to conform to the new panel format - *which means that older .organ files will be modified*! To ensure correct reading of (numerical) values from the .organ files, any leading or trailing whitespace as well as comments on the same line as a key/value pair will be stripped, even in the read source file! **Again, work on copies** as it's better to be safe than sorry. **You have been warned!** All that said, if you encounter problems that are repeatable, please report them as issues at https://github.com/larspalo/GOODF/issues so that the software might be improved.
15
15
16
-
A basic rendering of the GUI panels is now possible, but it likely still needs more work before it's fully reliable and usable. Presently only the transparency of .png files are likely to work, the masks of .bmp files needs more work to implement. Possibility to adjust positioning of smaller images and GUI elements directly on the graphical rendering is implemented since 0.7. Changing order of switches is implemented with drag and drop in the tree, note that in GrandOrgue it's only possible for a switch to reference another switch with a lower number than itself. If you drag switches to other positions references can be invalidated and removed (only the reference is removed, not any switch). Re-ordering of many other elements is possible with drag and drop since version 0.7.1.
16
+
Rendering of the GUI panels is now possible, but it likely needs more work before it's fully reliable. Possibility to adjust positioning of smaller images and GUI elements directly on the graphical rendering is implemented since 0.7 either with mouse or with arrow keys. Changing order of switches is implemented with drag and drop in the tree, note that in GrandOrgue it's only possible for a switch to reference another switch with a lower number than itself. If you drag switches to other positions references can be invalidated and removed (only the reference is removed, not any switch). Re-ordering of many other elements in the [Organ] tree with drag and drop can also be done.
17
17
18
18
## Future plans
19
-
Testing the ability to both write and read .organ files will need to continue so that they both works really well without any bugs. The graphical rendering of panels most likely needs more work so that it should display the panels exactly like GrandOrgue will. Improving/implementing new ways to assign properties/references to multiple elements instead of doing it one at a time is on the wish list.
19
+
Testing the ability to both write and read .organ files will need to continue so that they both works really well without any bugs. The graphical rendering of panels most likely still needs more work so that it should display the panels exactly like GrandOrgue will. Improving/implementing new ways to assign properties/references to multiple elements instead of doing it one at a time is on the wish list, this includes more flexible auto loading of pipes and copying options.
20
20
21
21
## Building from sources
22
22
Normal development tools for c++ is needed as well as cmake, imagemagic and wxWidgets.
wxMessageDialog dlg(this, wxT("ODF file is modified. Do you want to save/write it?"), wxT("ODF file is modified"), wxYES_NO|wxCENTRE|wxICON_EXCLAMATION);
361
+
if (dlg.ShowModal() == wxID_YES) {
362
+
// Try triggering save/write by posting an event
363
+
wxCommandEvent evt(wxEVT_MENU, ID_WRITE_ODF);
364
+
wxPostEvent(this, evt);
365
+
366
+
if (m_organ->isModified()) {
367
+
// This means that the save failed, ask if the user wants to abort the quitting to fix the issue
368
+
wxMessageDialog confirmDlg(this, wxT("ODF file couldn't be saved/written! Do you want to return to fix it before quitting?"), wxT("ODF file couldn't be saved"), wxYES_NO|wxCENTRE|wxICON_ERROR);
369
+
if (confirmDlg.ShowModal() == wxID_YES) {
370
+
return;
371
+
}
372
+
}
373
+
}
374
+
} */
356
375
// Destroy the frame
357
376
Close();
358
377
}
359
378
379
+
voidGOODFFrame::OnClose(wxCloseEvent& event) {
380
+
if (event.CanVeto() && m_organ->isModified()) {
381
+
// Ask if user wants to save/write the organ file
382
+
wxMessageDialog dlg(this, wxT("ODF file is modified. Do you want to save/write it?"), wxT("ODF file is modified"), wxYES_NO|wxCENTRE|wxICON_EXCLAMATION);
383
+
if (dlg.ShowModal() == wxID_YES) {
384
+
// Try triggering save/write by posting an event
385
+
wxCommandEvent evt(wxEVT_MENU, ID_WRITE_ODF);
386
+
wxPostEvent(this, evt);
387
+
388
+
if (m_organ->isModified()) {
389
+
// This means that the save failed, ask if the user wants to abort the quitting to fix the issue
390
+
wxMessageDialog confirmDlg(this, wxT("ODF file couldn't be saved/written! Do you want to return to fix it before quitting?"), wxT("ODF file couldn't be saved"), wxYES_NO|wxCENTRE|wxICON_ERROR);
0 commit comments