On Wed, Oct 01, 2008 at 03:06:34PM -0400, Mikus Grinbergs wrote: > [many rhetorical questions] > > > dbus-send --session --print-reply --reply-timeout=2000 \ > > --type=method_call --dest=org.laptop.sugar.DataStore \ > > /org/laptop/sugar/DataStore org.laptop.sugar.DataStore.unmount \ > > string:<datastore mount id> > > THIS is what I have the greatest amount of difficulty with. I fail > to see the necessity of users having to learn the "internals" of > dbus usage in order to be able to control their systems. If there > is a "knob" that users need to turn, DOCUMENT IT !!!
The journal UI lets you unmount one device already. It's documented already. Why is another way of doing it, automatable and suitable for very advanced users doing unusual things (like you), causing you difficulty? > Besides which, I have my removable storage devices mounted __for a > purpose__. [They contain software and data which I reference every > time I use the system.] I have no intention of unmounting them. So I'm puzzled as to why would you single out the launch feedback feature. I now understand that your XO's cpu is busy for reasons that you know about, and you're just noting that one UI feature that depends on being able to run quickly doesn't run so quickly when the cpu can't run it quickly. And that that happens only when you do something that most people don't do. Of course it'd be great if people could do that without such deleterious effects. > mikus Martin
pgpNTLJmSHqXW.pgp
Description: PGP signature
_______________________________________________ Sugar mailing list [email protected] http://lists.laptop.org/listinfo/sugar
