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
I think that the fact you cannot decide the name of the installed image is a big issue.
One of the most important advantages of OMB is that you can install several instances of the same enigma2 image in order, for instance, to make experiments or to test something.
But, despite of the fact you can change the filename of the zip installation file, OMB decide for itself how to name the new installed image in the list.
So if you have multiple instances of the same image, this makes very hard or almost impossible to distinguish them among the list.
Yes, you can rename them but AFTER you already are forced to see them named the same way.
There would be many ways of solving this issue but the simplest one, I believe, is to name the image exactly by the same name used for the zip filename. After all, the physical subfolder of OMB is named after the filename: why on earth not also the "descriptive" name in the list?
For example: if I renamed an image file as
OBH-4.4-2nd
why can't I have it named this way under the list of installed images?
This way I'd be completely free to have distinguishable installations.
Another solution, a little bit more complicated would be to show in the list produced by the GUI, next to the name, the folder where it is located. This way I'd be able to rename it accordingly without fearing of choosing the wrong one.
But why not directly the 1st method I suggested above? ;)
Regards
The text was updated successfully, but these errors were encountered:
I think that the fact you cannot decide the name of the installed image is a big issue.
One of the most important advantages of OMB is that you can install several instances of the same enigma2 image in order, for instance, to make experiments or to test something.
But, despite of the fact you can change the filename of the zip installation file, OMB decide for itself how to name the new installed image in the list.
So if you have multiple instances of the same image, this makes very hard or almost impossible to distinguish them among the list.
Yes, you can rename them but AFTER you already are forced to see them named the same way.
There would be many ways of solving this issue but the simplest one, I believe, is to name the image exactly by the same name used for the zip filename. After all, the physical subfolder of OMB is named after the filename: why on earth not also the "descriptive" name in the list?
For example: if I renamed an image file as
OBH-4.4-2nd
why can't I have it named this way under the list of installed images?
This way I'd be completely free to have distinguishable installations.
Another solution, a little bit more complicated would be to show in the list produced by the GUI, next to the name, the folder where it is located. This way I'd be able to rename it accordingly without fearing of choosing the wrong one.
But why not directly the 1st method I suggested above? ;)
Regards
The text was updated successfully, but these errors were encountered: