 |
I think that Cinelerra developers can solve this problem like this: The program when saving images can behave like this: 1) When you save a picture for the first time, the program displays the default path (as it does initially). 2) You install a new path for saving and tick the "User Path". The program remembers the new path and uses the new path in the following times. 3) Each time a user saves a picture, the program makes a check on the correctness of the "user path". 4) If the "User Path" is not true, then remove the check mark from the "User Path" in the menu of saving pictures. 5) When you remove the check mark from "User Path", the program inserts the default path in the field. This idea is good locally. Globally, I propose this implementation: In the settings, create a button for editing the database [Project Name - Path]. This database will determine in which cases for which projects which paths will be used in the first place, when the user wants to open, save, and so on. Are there two kinds of ways? 1) "Default Path" - the path that the program uses by default. 2) "User Path" - the path that the user sets independently. The database consists of the following columns. - Flag of changes - this flag is needed to determine in which lines the program found an error in the user's path and the program set the default path instead of the erroneous path of the user. - Path columns are columns that define paths of preservation and discovery. - Flags of paths - each column of paths has its own flag. These flags 2, here are their meanings - the "path is correct" and the "path is changed to the default path, since the" path of the user is "erroneous". When a user views a database in a window, these flags help to quickly visually determine where the "user path" was wrong. - A flag that has three states, here is their meaning: 1) Not saved and check required when saving. 2) Wrong "User Path". 3) "User Path" is correct. When does the program determine the correctness of the "user paths"? 1) When loading the program - for all paths. 2) When a user opens a window, open / save / ... before loading the window, open / save / ... 3) When the user clicked on the save button (since it takes some time between loading the window and pressing the "save" button, the folder in the "user path" may disappear). 4) When the user sets "User Paths" in the database. This happens when the user moves the focus from the field of the path to another field or to another area. When an error occurs, the physical error window appears and the save button becomes inaccessible. 5) When the user saves changes to the "Paths of users" and other fields that the user has changed. In this case, the program checks the correctness of the paths for those fields that the user has changed. When finding an erroneous path, make the "save" button inaccessible, show erroneous "user paths" with the icon, display messages that the changes have not been saved, correct the erroneous "User Paths". If the program found an erroneous "user path"? - The program changes in the database "user path" to "default path", as well as changes the corresponding flags. - If the program has found an erroneous "user path" during the program launch, a pulsating warning icon should appear on the main program window. The user can familiarize himself with the place where the program has changed due to the error "user path" to "default path" when the user clicks on the icon. - If the program found the error "user paths" during the opening of the open / save / ... window before opening the window (at this moment the program checked only one "user path"), then in the database, change the erroneous "user path" to " default path ", open / save / ... window to display a warning, open / save / ... window to change" user path "to" default path "that the user path for this window is wrong, and in the database This erroneous "user path" has been replaced with "default path". - If the program found an erroneous "user path" after the user clicked the "save" button (at this moment the program checked only one "user path"), then change the erroneous "user path" to the "default path" in the database , return the user to the save window, in the save window change the user's path to the default path, display a message in the save window that the user's path for this window is wrong, and this error path in the database user "has been replaced with" default path ". Database window [Project Name - Paths] All the flags that indicate that the user's path is not true, or the user's path is not saved, or the "user path" was changed by the program to the "default path" because the check revealed that the "User path" was erroneous, or the flag that indicates The fact that in this line of the record "User Path" was changed to "Default Path", because the check in this line revealed an erroneous "User Path" is shown by an icon next to the path field. The program does not show those fields that are correct. Also, the program does not show those lines in which the "User Paths" are correct. There is a list in the window that consists of the "Default Path" (this line is not displayed in the file where the database is stored, this data is stored in the program itself, this line cannot be edited), "New Project" and the names of the projects that the user has saved. This list is on the left. On the right are the description field, the path fields and the names of the fields in which the paths are located, as well as the name field in which the name that the user selected from the list is located. Next to the field there is an explorer icon with which the user can choose the path using the explorer. At the bottom is the button "save", "Copy path from", "Edit", "Delete". The "Delete" button is not available for the "New proket" Field "description" is not editable when "New project" is selected in the list. When "New project" is selected in the list, then in the "Description" field it is written: "" New project "is all projects that are not in the database list." At the bottom of the list there is a button "Create paths for a new project". Initially, the database is in browse mode. This means that the path fields, the explorer icons, the name field and the description field, the “save” button, the “Copy path from” button are not accessible from the beginning. The Edit button is not available for the "Default Path" list. The name field is a field in which the name of the project is written without its extension. When you click the "Edit" button, the list is blocked (the user cannot switch the base lines using the list until they save the changes), the "Create paths for a new project" button is blocked, the path fields, the name field, the icons of the conductors and the description field are unlocked ( descriptions and the name field is not unlocked for the line of the "new project" list), the "Copy path from" button is unlocked. When you click the "Save" button, the program checks the correctness of the path fields that the user has changed (when the field is changed, the program sets a special flag that this field is not saved and shows this as an icon), if the check did not find errors, then make changes to the database data, lock the "Save" button, "Copy path from", lock the path fields, lock the description, as well as the explorer buttons, unlock the list and unlock the "Create paths for a new project" button. Display a message that the new changes have been made to the database. When you click the "Copy path from" button, the program displays a window with the names of the path fields, check boxes next to the name fields, and on the left a list that corresponds to the list of the database window [Project Name - Path]. This allows you to copy paths from other fields of the list lines. That line of the list field that you are editing is in this window is grayed out and this line cannot be selected. When you click "New Project": 1) The name field is specified by the project name without an extension, checking the fields in the "New project" list (if there are incorrect path fields there, then the program in the database changes these paths to "default paths", changing the flags you need) in the database is written in a new line (project name and path fields, which are in the "New project" line) 2) The list is updated from the database. 3) goes to the line of the project that the program has just written to the database. 4) Press the "Edit" button, which performs the functions that I wrote above. When you click "Delete" 1) Displays a clarification message. The user confirms his intention to delete the line in the database. 2) The program deletes the line in the database. 3) In the database window, the program updates the list of strings from the database. In the database window you can also add a button to check all lists for correct paths. When errors are found, the erroneous "User Paths" will be changed to the "default paths", as well as the necessary flags are marked, and a warning window is displayed. And you can also add a button to check the correctness of the paths for the selected line. I think the second option is to decide the default paths in the global version. |
 |
When I do PrintScreen (screenshot) my Linux distro (UbuntuStudio_16.04) save the screenshot to the "/home/user/Pictures/" folder. I don't know if all Linux distribution have Pictures folder. If yes, then that folder could be good for Cinelerra-gg snapshots, I think. I would like another solution but it is child of of a my old request about Project and files folders structure (and relative path): https://lists.cinelerra-cv.org/pipermail/cinelerra/2018q3/009629.html |
- Anonymous
