GNOME Bugzilla – Bug 335816
Different drives should have different burn:// locations
Last modified: 2018-09-21 16:15:08 UTC
Please describe the problem: I have a USB DVD writer and an ATAPI CD writer. If I insert a DVD in the USB writer, open the CD/DVD creator and choose 'Write disc', the writer device is always chosen to be the ATAPI drive (which obviously cannot write DVDs). For me this is not a big problem, but it's confusing to other users who are not so clear about the difference between the two drives. I think that the writing device should default to the one where a disk was last inserted, if that is possible. Steps to reproduce: 1. 2. 3. Actual results: Expected results: Does this happen every time? Other information:
Hi, bug 309518 is similar and already has a patch. Do you think that that fix would be equally satisfactory?
I'm not quite sure. The CD writing process is very clear and intuitive right now: -insert blank CD -an icon appears on the desktop -open that and drag files into the folder -choose 'File/Write to disc' However, after the user chooses 'Write' in the resulting dialog, he may to his surprise realize that the wrong writer device was selected. Somehow you expect from the flow of the writing process that the right device will be chosen automatically. Of course I realize that this may not be easy to implement.
Thanks for the explanation! I think that the solution would be to associate different burn:// location to each drive (I was thinking about filing a bug for that myself) i.e.: When you click on "blank disc" (writer1) on the desktop and the burn location for writer1 opens. Burning sould be "spatial" as well. This can help us to fix bug 332532, bug 300021 and this way you can write two disc at the same time if you own two writers as well.
That sounds like an excellent solution. Thanks.
Re-titling.
Instead of a "CD/DVD creator", nautilus-cd-burner should use the driver icon on Desktop. Some tasks examples: 1 - You insert a blank CD/DVD into the driver to write some files. - an icon appears on the desktop that show the type of the disc ( CD-R, CD-RW, DVD-R, DVD-RW ) - open that and you see the freespace on the disc. - drag files into the folder and you see space information (bargraph) - choose 'File/Write to disc' 2 - You insert a CD/DVD with previous sessions on the driver. - an icon appears on the desktop and show the type of the disc ( CD-R, CD-RW, DVD-R, DVD-RW ) - open that and you see the freespace and the files already on the disc. - drag files into the folder. (the new file should be semi-transparent) - choose 'File/Write to disc' 3 - You dont have a disk on the driver and want to prepare the data to write in the CD/DVD. - Nautilus should show the icon driver on desktop when it aren't mounted. - open that and drag files into the folder. - until you insert a CD/DVD on the driver the 'File/Write to disc' button are disabled.
I read all of your comments. This is my first contact with gnome-vfs and nautilus. But I think I could make some working stuff. I would like to make different rootnode for every device, like this: mapping-method.c: static GnomeVFSResult do_open_directory (GnomeVFSMethod *method, GnomeVFSMethodHandle **method_handle, GnomeVFSURI *uri, GnomeVFSFileInfoOptions options, GnomeVFSContext *context) { (...) device_str = gnome_vfs_uri_get_host_name(uri); if (device_str == NULL) { /* this is just burn:/// show only devices */ NautilusBurnDrive *drive; GList *l = nautilus_burn_drive_monitor_get_drives(drive_monitor); (... make list of drives ...) } else { /* this is burn//device_name/some_path/ show content from mapping-daemon */ res = request_op (MAPPING_PROTOCOL_OP_LIST_DIR, g_strdup(device_str), path, NULL, FALSE, NULL, &reply); (... if I good understand code of mapping-daemon, he make different rootnode per method (device_str in this case) ...) } So, choose of the device never be in nautilus-burn-drive-selection, he will be choose already before you click on burn button. Every icons which representating clean cd/dvd should open burn://device_name/ instead of burn:/// This clear way to implement multisessions :) Thats be ok ?
Created attachment 99822 [details] preview of how nautilus-cd-burning may work
Created attachment 99823 [details] [review] code preview of how nautilus-cd-burning may work I work on this, and this is result. Of corse this is not working yet, but only preview. I am new in gnome programming, so please comment this. I think I must write some more pretty VirtualFile support (maybe gobject compatible). Drive monitor shall be move from nautilus-burn to mapping module...
it is great to see someone working on this... however just a warning maybe: gnome-vfs is being removed from nautilus. in the next gnome version it will be replaced by GIO. so maybe don't base too much your work on gnome-vfs. maybe you should focus on making it work on the nautilus-gio development branch. blog of nautilus maintainer discussing the changes: http://blogs.gnome.org/alexl/ if that is irrelevant to your efforts, ignore this. i'm not sure whether it's relevant, i just didn't want that you do work for nothing.
I don't think having multiple burn locations is a good idea. It can cause a lot of problems if you access the burn locations in different ways. For instance, if you first open it from the menu and add stuff to it, then insert a blank cd you'll get a new blank burn:/// tree separate from the one you set up. However, it would be good to connect the drive to the burn location. We should add a way to tell the burn backend what the default drive is, and whenever a blank disk is inserted in a drive and the volume of that is pointed to the burn mount we set the default drive to that one, so that when burn is selected the right default drive is choosen.
-> gvfs Moving to the gvfs burn backend.
Comment on attachment 99823 [details] [review] code preview of how nautilus-cd-burning may work The patch is for Gnome VFS so setting status to "needs-work" to get it off the review list.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gvfs/issues/26.