askYesNo()

[meik michalke]

hi,

Am Mittwoch, 9. Mai 2018, 09:15:00 CEST schrieb Thomas Friedrichsmeier:
> In fact, I'm wondering whether it would make sense - or more precisely
> whether it would be worth the trouble - to adjust rk.show.question()
> itself to NA as return value for "Cancel". (For better drop-in
> compatibility with askYesNo(), but, admittedly NA seems a better choice
> than NULL, here).
> 
> Of course for backwards compatibility, that would mean adding a new
> function with that return value (say rk.ask.question()), deprecating
> rk.show.question(), and removing it in the future...

that's an even better idea. i've pushed something for testing, i just called 
the new function rk.askYesNo() and modelled its arguments after askYesNo().

please check it out!


viele grüße :: m.eik

-- 
  dipl. psych. meik michalke
  institut f"ur experimentelle psychologie
  abt. f"ur diagnostik und differentielle psychologie
  heinrich-heine-universit"at d-40204 d"usseldorf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/rkward-devel/attachments/20180516/17cacabc/attachment.sig>