In addition to the current Message Requester Options:
#PB_MessageRequester_YesNo : to have 'yes' and 'no' buttons
#PB_MessageRequester_YesNoCancel : to have 'yes', 'no' and 'cancel' buttons
#PB_MessageRequester_Ok : to have the 'ok' only button
These are often seen in apps and in Windows OS:
#PB_MessageRequester_YesYesToAll : to have 'yes' and 'yes to all' buttons
#PB_MessageRequester_NoNoToAll : to have 'no' and 'no to all' buttons
#PB_MessageRequester_YesYesToAllCancel : to have 'yes', 'yes to all' and 'cancel' buttons
#PB_MessageRequester_NoNoToAllCancel : to have 'no', 'no to all' and 'cancel' buttons
#PB_MessageRequester_YesYesToAllNoNoToAllCancel : to have all yes/no permutations
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
It doesn't support them because they're not cross-platform.
There are many things that are not cross-platform. The team either roll their own cross-platform version or make a note in the Help - so this would be no different.
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
IdeasVacuum wrote:These are often seen in apps and in Windows OS:
#PB_MessageRequester_YesYesToAll : to have 'yes' and 'yes to all' buttons
#PB_MessageRequester_NoNoToAll : to have 'no' and 'no to all' buttons
#PB_MessageRequester_YesYesToAllCancel : to have 'yes', 'yes to all' and 'cancel' buttons
#PB_MessageRequester_NoNoToAllCancel : to have 'no', 'no to all' and 'cancel' buttons
#PB_MessageRequester_YesYesToAllNoNoToAllCancel : to have all yes/no permutations
Maybe it is custom dialog boxes? MessageBox() does not define "YesToAll" or "NoToAll".
I don't know what the name of the control is - could indeed be custom, but there seems to be a lot around that are the same - maybe they are based on an MSDN custom example somewhere.
Anyway, thinking about it, the list for MessageRequester() features is never-ending, and no matter what Fred bolts-on, there will always be something else needed by somebody - So I think this request is Null and Void. If we want a Requester that is different from the standard one, we just have to code it ourselves.
IdeasVacuum
If it sounds simple, you have not grasped the complexity.
> Anyway, thinking about it, the list for MessageRequester() features is never-ending,
> and no matter what Fred bolts-on, there will always be something else needed by
> somebody - So I think this request is Null and Void
LOL, you just posted what I said about MessageRequester flags over a decade ago:
