View Single Post
Posts: 462 | Thanked: 550 times | Joined on Sep 2008 @ Moscow
#215
Originally Posted by Mentalist Traceur View Post
Keep in mind, that because buttons are so small in status menu, operator name doesn't fit and you end up being unable to see the connected/unconnected bit of info at a glance.

So I think it's great that it shows operator name in the notification messages, but I think it should stick to just showing "<>" in the status menu button when connected.
Good point, I'll think about improvements during weekend

Originally Posted by Mentalist Traceur View Post
While we're on the subject, the JP setting is currently not supported in the injection capable driver (I have no desire to call it bleeding edge at this point, it's ~ a year old by now). I believe the regulatory region for that driver is hardcoded.

So that leads me to point out that if you have support for custom scripts, I hope you remember to make them flexible enough to be able to decide if they fire on events for either wifi driver, or for both.
At the moment scripts are flexible enough
5 main events:
1. if down (/usr/bin/advifsw/post-down)
2. loaded default driver (/usr/bin/advifsw/post-load0)
3. loaded injection driver (/usr/bin/advifsw/post-load1)
4. unloaded driver (/usr/bin/advifsw/post-unload)
5. if up (/usr/bin/advifsw/post-up)

In those dirs you can put your scripts (don't forget to +x them).
 

The Following 4 Users Say Thank You to 412b For This Useful Post: