If the Action Name "open" is hard coded, then how is it that the default Device Action for Amarok had "play" as the action?

Well, both solutions have 'issues.' Each one does work, but only for the first music CD. If you then eject the CD and close Amarok, then insert a different music CD and choose either of the notification items (I have both), Amarok launches but does not identify or load the CD.

I tried the edit in Fedora 12. Unfortunately it still doesn't fix the problem for me. From the notifier, amarok does indeed launch, but it continues by playing whatever playlist was last used. If I navigate through Local Music > Audio CD it tells me that there are 0 tracks. Going through Amarok > Play Media > Audio CD causes a pop-up

Error - Amarok

Device does not have read permissions for this account. Check the read permissions on the device.

Anything more that I can try?

Back to the initial topic:

Ignacio Serantes wrote:For example, if I connect my camera, open with Dolphin could be stupid so disable this action easily and maintain only "Download Photos with digikam" would be developed. Probably is the thing you want to do so, an additional form and a click is a lost of time any time you plug your camera.

The same for an usb player or for usb harddisks. If I plug my mp3 player the only action I need is Amarok but if I plug my external hard drive probably I want to launch Dolphin.

What I understand from this is that you want a "remember this action" in the Device Notifier.

I hadn't noticed that this feature was missing (because I hardly use it in other DE) but I guess it's quite handy

Jonan wrote:Back to the initial topic:

Ignacio Serantes wrote:For example, if I connect my camera, open with Dolphin could be stupid so disable this action easily and maintain only "Download Photos with digikam" would be developed. Probably is the thing you want to do so, an additional form and a click is a lost of time any time you plug your camera.

The same for an usb player or for usb harddisks. If I plug my mp3 player the only action I need is Amarok but if I plug my external hard drive probably I want to launch Dolphin.

What I understand from this is that you want a "remember this action" in the Device Notifier.

I hadn't noticed that this feature was missing (because I hardly use it in other DE) but I guess it's quite handy

Yes, you understand me .

For example, in KDE 4.4 device notifier things are better than in KDE 4.3 but I think that is not perfect. If I wan't to open a device with dolphin I must do the next:

1) Click over "Device notifier" icon.
2) Click over device so I can see posible actions.
3) Click over the action.

So I count three mouse clicks. If you change the things a few, using right or middle click to display device actions you can do the same with only two clicks.

1) Click over "Device notifier" icon.
2) Click over device: first time device actions are displayed so you can select your favourite action for that device and, when this action was selected always is used for that device).

Think that the next time you plug that device you probably want to use the same action again and, probably, you don't use several actions for the same device.

Really the same method is using on all desktops with files. With click you open a file with default action and, if you want other action you must use right click button.

annew wrote:amarok does indeed launch, but it continues by playing whatever playlist was last used.

This was reported to me as well. One has to actually close Amarok (after having ejected the CD), insert a new music CD, relaunch via the Device Notifier action. And even this doesn't always work. I've found that doing this may (or may not) have the CD identified and the album/tracks shown, and if shown, might be for the 'previously' loaded CD.

As the Device Action merely 'hands off' control to the called application, this implies something is still wrong with the way Amarok handles identification of CDs. The exhibited behavior is a lot like what (used) to happen when working with floppy disks. Insert and work with a floppy. Eject it and insert a new diskette, and you would 'see' what had been on the previous diskette. The issue then, was the flushing of the read/write cache. That issue was resolved by the 'Safely Remove' action on a mounted removable device, which flushes the cache of any unwritten changes before it unmounts it. I wonder if this behavior is occurring with Amarok. It certainly appears to be the case.

Hi, everybody!
I find the device-manager settings much too complicated, without proper explanations. They aren't for the regular users. The KDE 3 was more intelligent. I could tell the system to open DVD/CD always upon insertion, without boring and unwanted pop-ups of the plasma, I could define default AND AUTOMATED actions for different types of media.

With KDE 4 all that has gone. Although I have degree in math I cannot figure how to set up actions. Please descend from the heavens and make apps for earthly users. And remember: YOU are the developers, BUT WE ARE the users. And we need basic stuffs. I'm using KDE 4.4.2 and I need:
- removable media automatically opened in Dolphin
- movie DVD opened automatically with one of my favorite applications
- AudioCD opened automatically with one of my favorite applications
- Camera opened automatically with one of my favorite applications

An example: When I grab a CD/DVD it can happen that:
a). I want to open a document, movie, image etc. So I intend to open it with a file browser.
b). I want to watch a good movie on a DVD. So I intend to place it into tray, close the tray and lean back and enjoy the it in Xine or other app.
c). I want to listen to an audio CD of mine. So I intend to place it into the tray and to go doing my job, listening to the music with Amarok.

Simplicity!

Everything beyond that is wasting your time and playing with our nerves!

Note that it isn't possible to automatically run applications. The support simply isn't there, since it was never requested.

You should be able to use the Device Actions control module however to create the actions that you need...

The support simply isn't there, since it was never requested.

This is a very odd fact. It existed in KDE 3.5 and worked quite well. This is a regression to it. And you say it is possible to achieve my goals with the Device Manager. But how? There are so many possibilities for an action and it is nowhere explained. I understand that the designers wanted to create something flexible, but they missed the point, that this labyrinth of conditions is rather confusing and very annoying. People doesn't want complicated things, and unfortunately this Device Manager IS complicated.
Any readings about the thoughts of the developers? At least to understand what they are intend to do, or the philosophy of KDE 4's device managing.

I believe the change in concepts for the framework was because the older framework did not allow for devices to be tested suitably to ensure launching the application is relevant.

With regards to creating the actions, the following should be sufficient:
The fields should be filled in the following order: Parameter Type, Device Type, Value Name, Dropdown menu beside text field, text field.

- removable media automatically opened in Dolphin

Create an action, with the top level item being set to "Property Match > Storage Volume > Usage > Equals > FileSystem"

- movie DVD opened automatically with one of my favorite applications

Create an action, with the top level item being set to "Property Match > Optical Disc > Available Content > Equals > Data|VideoDvd"

- AudioCD opened automatically with one of my favorite applications

Create an action, with the top level item being set to "Property Match > Optical Disc > Available Content > Equals > Audio"

- Camera opened automatically with one of my favorite applications

Create an action, with the top level item being set to "Device Interface Match > Camera"

NOTE: This will simply make your devices accessible with the preferred applications, they will not autorun, please file a wish a bugs.kde.org for that to be possible.