----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102157/#review5473 -----------------------------------------------------------
libs/ui/security/eapmethodstack.h <http://git.reviewboard.kde.org/r/102157/#comment4917> Qt's classes also inherit signals, since this one has been declared in SecurityWidget you do not need to declare it again. libs/ui/security/leapauthwidget.h <http://git.reviewboard.kde.org/r/102157/#comment4909> Qt's classes also inherit signals, since this one has been declared in SecurityWidget you do not need to declare it again. libs/ui/security/nullsecuritywidget.h <http://git.reviewboard.kde.org/r/102157/#comment4911> Use Q_SIGNALS to follow code style (below we use Q_SLOTS). libs/ui/security/securityleap.h <http://git.reviewboard.kde.org/r/102157/#comment4913> Use Q_SIGNALS to follow code style (below we use Q_SLOTS). libs/ui/security/securitywidget.h <http://git.reviewboard.kde.org/r/102157/#comment4916> I think "connected" is more used than "hooked" when talking about signals and slots. libs/ui/security/securitywidget.h <http://git.reviewboard.kde.org/r/102157/#comment4912> Use Q_SIGNALS to follow code style (below we use Q_SLOTS). libs/ui/security/wepauthwidget.h <http://git.reviewboard.kde.org/r/102157/#comment4914> Use Q_SIGNALS to follow code style (below we use Q_SLOTS). libs/ui/security/wepwidget.h <http://git.reviewboard.kde.org/r/102157/#comment4918> Qt's classes also inherit signals, since this one has been declared in SecurityWidget you do not need to declare it again. libs/ui/security/wirelesssecuritysettingwidget.cpp <http://git.reviewboard.kde.org/r/102157/#comment4908> "signal". Anyway, I think this comment is not necessary. libs/ui/security/wpaauthwidget.h <http://git.reviewboard.kde.org/r/102157/#comment4915> Use Q_SIGNALS to follow code style (below we use Q_SLOTS). - Lamarque Vieira On Aug. 6, 2011, 10:39 a.m., Rajeesh K Nambiar wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://git.reviewboard.kde.org/r/102157/ > ----------------------------------------------------------- > > (Updated Aug. 6, 2011, 10:39 a.m.) > > > Review request for Network Management. > > > Summary > ------- > > WEP key validation (should have only 5 to 13 ASCII characters for Ascii key; > and 10 to 26 Hex characters for Hex key) wasn't working. Most of the bits > were present, here's a gross hack to make it really work. Only implemented > and tested WEP validation, but can be extended for other security types as > well. > > I'm not sure this could be the best/easiest implementation, spent a night > figuring out the right signal/slots :-). If this hack could be refined, > please let me know! > > > Diffs > ----- > > libs/ui/security/eapmethodstack.h 552f5c9 > libs/ui/security/leapauthwidget.h 3c01e1d > libs/ui/security/nullsecuritywidget.h dc84fb5 > libs/ui/security/securityleap.h 402a7af > libs/ui/security/securitywidget.h c536cf6 > libs/ui/security/wepauthwidget.h 6ff721b > libs/ui/security/wepwidget.h e78338c > libs/ui/security/wepwidget.cpp f024555 > libs/ui/security/wirelesssecuritysettingwidget.cpp fbc2c34 > libs/ui/security/wpaauthwidget.h 91e7495 > libs/ui/security/wpapskwidget.h 7077836 > > Diff: http://git.reviewboard.kde.org/r/102157/diff > > > Testing > ------- > > Tested with WEP Hex and ASCII key validations. "OK" button of connection > editor widget is now properly enabled/disabled upon changing key. > > > Thanks, > > Rajeesh > >
_______________________________________________ kde-networkmanager mailing list [email protected] https://mail.kde.org/mailman/listinfo/kde-networkmanager
