Extended Message Box - New Version: 16 Feb 24

[KaFu]

On my homebox I'm running Win7-64, currently I'm working on a XP-32 machine (might be the reason for the differences!), I'll recheck later in the evening when I'm at home.

If your standard is "Segoe UI, 9" and you get "MS Shell Dlg, 8" from my code, this indicates that it returns an error on Vista. Rerun attached code and look at console for error.

By the way, I always thought that MS Shell Dlg and MS Shell Dlg2 were shorthand for the real font names stored under

They are, but "MS Shell Dlg" is what my function returns, thus I hardcoded it as the error-substitute too... that one might need an @OSType switch?

HKLM\Software\Microsoft\Windows NT\Currentversion\FontSubstitutes - I have MS Sans Serif and Tahoma as the values in my registry.

Exactly the same here on XP.

Are you sure that MsgBoxes use the default GUI font? It does not appear so on my machine and I know I spent considerable time searching for the default MsgBox font location when I first wrote the UDF.

Nope, can't put my finger on it yet... but see these screenshots, a ) your UDF, b ) my alteration and c ) standard msgbox... hell, even my result does not look 100% the same as the standard (font width?)

Does my original _GetDefaultEMBFont function return data from the $tNONCLIENTMETRICS structure or from the @error default for you

Works and returns Tahoma/9 for me (which is definitely not the font of the standard msgbox on this xp installation).

Definitely does not happen for me with either the original or your version. The EMB comes up in the default "whitish" colour all the time.

I'll have to dig into that.

Please do not think I am not being defensive here, I would like to get the bottom of it but it is a bit difficult if I cannot reproduce the problems you are having.

Never ever m8 , just want to "fix" a possible error (on my side?) in this great function to use it myself ...

Some minor adjustments (changed ref ctrl from button to label), added some debug consolewrites...

[KaFu]

After some research...

This RegKey seems to set the default MsgBox() font and fontsize on XP... I guess it's linked to the "Window Theme".

[HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics] "MessageFont"

It's neither the "Tahoma/9" detected by your UDF nor my "MS Shell Dlg/8", it's "Tahoma/8" here (with "MS Shell Dlg2" = "Tahoma"?)... *sigh*...

So... googleing around brought me to this:

http://msdn.microsoft.com/en-us/library/aa511282.aspx

"Choose fonts and optimize window layouts based on the UI technology and the target version of Windows" ... different OS, different source for default fonts...

But where there is darkness, there is light ...

"Developers: From code, you can determine the system font properties (including its size) using the GetThemeFont API function. You can determine the system colors using the GetThemeSysColor API function."

http://msdn.microsoft.com/en-us/library/bb759745(VS.85).aspx

Which might be the way to go?

Edit:

And a quick googleing on that keyword:

http://www.google.com/search?q=GetThemeFont+autoit

Shows that someone on the German autoit.de forum has already coded a great start ...

(to be continued...)

Edited January 19, 2011 by KaFu

[xrxca]

Great UDF, much easier than a custom GUI for every odd messagebox, I have a couple of minor suggestions.

• The ability to change the message font/size, but leave the buttons the default font.

  I'm using a script that displays a Well UWI and ask the user to confirm the change, and for clarity I specify a larger fixed width font for the UWI which looks rather silly on the buttons.

  (I modified my copy by adding an extra Global var and an option to _ExtMsgBoxSet and changing the GUISetFont call accordingly)

• Adjust the button size if the button text will not fit (this can be a real problem if the font has been changed)

• The ability to specify a custom icon (Maybe pass an icon filename/iconid instead of the icon flag# ?)

• Be a little more forgiving on message text width, One of the messages my script used includes a variable length id with no spaces in it and on occasion is slightly too long and _ExtMsgBox throws an error 5 because the call to _StringSize returned error 4

  I've modified my copy to increase the width in increments of 50 up to a max of 500 if this happens.

  Local $aLabel_Pos = _StringSize($sText, $iEMB_Font_Size, Default, Default, $sEMB_Font_Name, $iMsg_Width_max - 20 - $iIcon_Reduction)
  while ( @error == 4 ) and ( $iMsg_Width_max < 500 )
      $iMsg_Width_max += 50
      $aLabel_Pos = _StringSize($sText, $iEMB_Font_Size, Default, Default, $sEMB_Font_Name, $iMsg_Width_max - 20 - $iIcon_Reduction)
  wend
  if @error then
      $nOldOpt = Opt('GUIOnEventMode', $nOldOpt)
      Return SetError(5, 0, -1)
  endif

  Not the cleanest solution, but it works for me.

[Melba23]

xrxca,

Great UDF [...] I have a couple of minor suggestions

That is the way to get your suggestions listened to!

- 1. The ability to change the message font/size, but leave the buttons the default font.

Done - you need to add 4 to the $iStyle parameter in the _ExtMsgBoxSet function - 1 and 2 are already used for TaskBar appearance and TOPMOST.

- 2. Adjust the button size if the button text will not fit.

Not prepared to do this - the EMB size computations would become horrendous. However, I have changed the logic of the overall sizing process: even if the text itself does not require the preset max width of the EMB to display, the EMB will expand to allow buttons to display at the maximum available size that will fit within that preset max width rather the minimum size as was the case. Basically, you get bigger buttons even with short text.

- 3. The ability to specify a custom icon.

Done. I have had this in my Toast UDF for ages - I cannot think why it was not in this one. Just add the filename of an exe or an icon rather than teh numeric value and it displays.

- 4. Be a little more forgiving on message text width

Done. There is a new variable in the _ExtMsgBox function - $iMsg_Width_abs - which is the absolute max value permitted. As with your code, if you get a StringSize error, the EMB expands up to that absolute value in steps of 10 to try and fit in a long unbroken string.

So 3 out of 4 - and some help towards the fourth. I told you that flattery would get you listened to!

M23

Edit: New files in first post.

Edited January 31, 2011 by Melba23

[Scan]

woow .. great jop

But when i run script .. this massage came :|

note : autoit setup { lastest verson ) & SciTE4AutoIt3 ( lastest also )

So the Problem from where ?

[Melba23]

Scan,

Just change the line to read #include "ExtMsgBox.au3".

I had mistakenly included the testing example in the zip - it is now corrected. Thanks for pointing it out.

M23

[Scan]

The re-emergence of error come's again !!

with this massage ?

I have tried adjustment but undeveloped !!

i have change the line but Without new-happens !!

so u can make me know the problem from where

when i change line same error come in a Another line ?

Best regards

[BrewManNH]

If you've followed the instructions in the first post and downloaded the StringSize.au3 file and placed it in the same folder as the UDF then you can change that line to #include "StringSize.au3" instead of using the "< >".

[Scan]

If you've followed the instructions in the first post and downloaded the StringSize.au3 file and placed it in the same folder as the UDF then you can change that line to #include "StringSize.au3" instead of using the "< >".

thank u very match

now it's working .. I forgot that we must call the file StringSize.au3

Until the script works well

But may I ask ?

what's the reason for collecting the files ( aut.3 ) in the same folder |!

Edited February 5, 2011 by Scan

[Melba23]

Scan,

what's the reason for collecting the files ( aut.3 ) in the same folder

Because it is the easiest way to make sure new users have the #include files available to run the example. If the #include files are in the same folder as the script they are always visible to it.

But did you know you can set specific folders that AutoIt will search for #include files as well as the standard "C:\Program Files\AutoIt3\Include"?

From the Help file:

"There is a special registry value that can be created at "HKEY_CURRENT_USER\Software\AutoIt v3\AutoIt" called "Include". It should be a REG_SZ (string) value. The contents of this value are a semi-colon delimited list of directories that should be searched for files when resolving #include's in addition to the standard locations."

If you have the full SciTE4AutoIt3 editor, you can also set this folder in SciTEConfig - look in the <Tools> menu.

So you can put all your downloaded includes into a folder away from "C:Program Files" - and it will not be overwritten when you next update!

All clear?

M23

[Scan]

Scan,

Because it is the easiest way to make sure new users have the #include files available to run the example. If the #include files are in the same folder as the script they are always visible to it.

But did you know you can set specific folders that AutoIt will search for #include files as well as the standard "C:\Program Files\AutoIt3\Include"?

From the Help file:

"There is a special registry value that can be created at "HKEY_CURRENT_USER\Software\AutoIt v3\AutoIt" called "Include". It should be a REG_SZ (string) value. The contents of this value are a semi-colon delimited list of directories that should be searched for files when resolving #include's in addition to the standard locations."

If you have the full SciTE4AutoIt3 editor, you can also set this folder in SciTEConfig - look in the <Tools> menu.

So you can put all your downloaded includes into a folder away from "C:Program Files" - and it will not be overwritten when you next update!

All clear?

M23

clear , clear (K) ..

many thx m23

[Melba23]

Hi,

NEW VERSION released 8 Feb 11.

Added: Countdown option. Seconds to go is displayed in place of an icon - see Test 3 in the example.

Some minor code changes. As usual, no need to change anything in your current scripts - just use the new option if you need it.

New files and zip in first post.

M23

[KaFu]

Nice . I think the default color needs conversion.

Global $iDef_EMB_BkCol = DllCall("User32.dll", "int", "GetSysColor", "int", 15) ; $COLOR_3DFACE = 15
$iDef_EMB_BkCol = RGB2BGR($iDef_EMB_BkCol[0])
Global $iDef_EMB_Col   = DllCall("User32.dll", "int", "GetSysColor", "int", 8) ; $COLOR_WINDOWTEXT = 8
$iDef_EMB_Col = RGB2BGR($iDef_EMB_Col[0])

Func RGB2BGR($iColor)
    Return BitAND(BitShift(String(Binary($iColor)), 8), 0xFFFFFF)
EndFunc   ;==>RGB2BGR

[Melba23]

KaFu,

You obviously have non-symmetric hex default colours then! I get the Windows default 0xF0F0F0 and 0x000000 so I see no difference.

Looks like another release later today. Thanks for pointing it out.

M23

Edit: Done - first post updated.

Edited February 8, 2011 by Melba23

[KaFu]

Currently running XP: Windows XP Style => Default (blue)

15: returns 0xD8E9EC, should be 0xECE9D8

8: returns 0x000000 (but I guess a conversion is still appropriate )

[Melba23]

Deleted uncorrected double post - when will we get the "delete post" function working again?

M23

Edited February 8, 2011 by Melba23

[Melba23]

KaFu,

I take it the new upload works as you expect?

M23

Edit: Typnig

[KaFu]

It does ...

[Melba23]

KaFu,

Good!

M23

[wakillon]

Hi Melba !

Nice Work !

I read your topic for knowing if there is a way to set Font weight, but unsuccesfully...

And The box depth should be adjusted to fit but when i tried :

#include <ExtMsgBox.au3>

$_YoutubeUrl = 'http://www.youtube.com/watch?v=XPBwXKgDTdE'
_ExtMsgBoxSet ( 3, 0, 0xFFFF00, 0xFF0000, 12, "MS Sans Serif" )
$sMsg = $_YoutubeUrl & @CRLF
$sMsg &= "Do you want download it ?"
$iRetValue = _ExtMsgBox ( 128, "Yes|No", "Match !", $sMsg, 10 )
ConsoleWrite ( "$iRetValue : " & $iRetValue & @CRLF )

Nothing happens, i must set fontsize to 9 for get it working...

And changing font size and font weight is for me the main interest of your ExtMsgBox !

Edited February 20, 2011 by wakillon