dionel1969 Posted December 26, 2011 Share Posted December 26, 2011 Hello: It is possible to do this procedure AskAsConfirmationA(const aMsg: String; aCallBack: TUniDialogCallBackAnonProc); inline; begin MessageDlg(aMsg, mtConfirmation, [mbYes,mbNo], aCallBack); end; ???? Quote Link to comment Share on other sites More sharing options...
Administrators Farshad Mohajeri Posted December 27, 2011 Administrators Share Posted December 27, 2011 Have you tested it? Quote Link to comment Share on other sites More sharing options...
dionel1969 Posted December 27, 2011 Author Share Posted December 27, 2011 Have you tested it? Yes, of course and it does not work. I have a unit with some "proxy" functions or procedures to avoid write some parameters for example: procedure AskAsConfirmation(const aMsg: String; aCallBack: TXXXXX); inline; procedure AskAsError(const aMsg: String; aCallBack: TXXXXX); inline; procedure ShowWarning(.... and so on. They are inline procedures, so they do not generate extra "call codes", just to avoid write [mbYes, mbNo], mtWarning or mtConfirmation and so on all the time. Just for commodity. In this case it does not work. Prueba de Anonymous Proc.rar Quote Link to comment Share on other sites More sharing options...
Administrators Farshad Mohajeri Posted January 3, 2012 Administrators Share Posted January 3, 2012 Your test case works perfectly in XE. Quote Link to comment Share on other sites More sharing options...
dionel1969 Posted January 4, 2012 Author Share Posted January 4, 2012 Your test case works perfectly in XE. Then, I have to migrate from 2009 TO XE. ja ajajajaj. Let's see in the near future. It is not a a big reason, but is one more. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.