> Both on; Wireless on, bluetooth off; Bluetooth on, wireless off; Both off
In that case, IMHO, we should do that. Probably best to file a bug that
says that is what the behaviour positively should be
The only complication is that it requires state saving (or it might not, if
the state of both wireless and bluetooth can be acquired. The Bluetooth
state can be got easily but for the wireless it calls out and depends on
another script.
-Paul
--
Britain is just cold, in a pesky way. Nottingham, GB
> Both on; Wireless on, bluetooth off; Bluetooth on, wireless off; Both off
In that case, IMHO, we should do that. Probably best to file a bug that
says that is what the behaviour positively should be
The only complication is that it requires state saving (or it might not, if
the state of both wireless and bluetooth can be acquired. The Bluetooth
state can be got easily but for the wireless it calls out and depends on
another script.
-Paul
--
Britain is just cold, in a pesky way. Nottingham, GB