Leaderboard

[NEW VERSION] - 17 Mar 22 Added: A new function _Notify_Size which allows you to adjust the size of the notification from its default 160x40. Please read the function header to see the max/min sizes that you can set for the width and height - the function returns informative @error/@extended values if these are not respected. Regardless of the size set, each notification will still display only 2 lines of text with the size of font used set automatically by the UDF. New UDF in the zip below. Previous changes: Changelog.txt A while ago I was asked to help port an AHK UDF to AutoIt. This was not too difficult and I found it useful myself (as a replacement for ConsoleWrite when debugging compiled scripts among other things). I have been polishing it for a while and thought I might release it in case it proves useful to anyone else. The notifications produced by Notify are small 2-line boxes that pop out of the edge of the display one above the other (you can select which side and in which direction they appear) - you can have as many as you want although only as many as can fit on your display will appear, the others will appear as soon as there is room. You can select whether they will retract after a certain time and/or when clicked. Colours and font are user-definable, and you can add an icon or image (bmp, jpg, gif or png) if you wish. When a notification retracts, the others move to leave space for more (you can select a smoooth slide or an instant move) - run the examples to see them in action. If you find the default sizing of the notifications is not to your liking you can change it by amending these values in the UDF (lines #354-356): ; Set default auto-sizing Notify dimensions Local $iNotify_Width_max = 300 Local $iNotify_Width_min = 150 Local $iNotify_Height = 40 A zip containing the UDF, example scripts and my StringSize UDF (which is also required): Notify.zip As usual happy for comments and/or compliments. M23

argumentum, That code looks like the answer (allowing for my error in labelling the columns) - I will now try and integrate that into a function within the UDF. But please do not hold your breath - I am quite busy for the next few days. M23

argumentum, Great! Problem already solved before it existed - I like that! M23

argumentum, The simplest way to "prettify" it is for you to use the existing _Notify_Locate function to change the position of the notifications to the left edge of your screen. But I will look into how the UDF might take account of additional screens. M23

guinness, That colour scheme looks very much like mine - so lay off! M23

From the help file: Optional parameters are defined by assigning a default value to them. The value may be a global variable, macro or literal value. Optional parameters always appear last in the function definition. All parameters added after the first optional parameter must also be optional. Your second parameter is optional. Therefore, the third parameter also needs to be optional or you should swap them around so that the optional one is last.

[NEW VERSION] - 7 May 15 Changed: New code to prevent multiple clicks overwhelming the UDF - further clicks now ignored if a notification is extending/retracting. New UDF in the first post. M23

rajah, You have been reported for sending PMs asking for help. Please read the Forum rules when you log back into the forum - you will see that we do not permit that here. Asking for help via PM is discouraged because the forum is here to help everyone - if you get private help then no-one else can benefit. So please do not do it again - just post in the forum and someone will help you. M23

Okay, if you're serious about an immediate patch, open MCF.au3, find UDF _EncodeMCF(), locate the section headed "; replace all strings", and look for If $prevchar="," Or $prevchar="&" Thenand replace it with If $prevchar="&" ThenI haven't tested this at all, and haven't looked at MCF.au3 in many months, but I think a patch along these lines should disable all multiline breaks after commas, within strings at least. Not sure whether there are other instances that have to be patched as well. When I have some spare time, I'll make a separate switch for this.

Oh and I guess you have a small test script, therefore could you post it all instead of a small snippet. It's just that the code you posted makes no sense to a new user, without an overall view of the code beforehand. Plus think how you would feel if you came across a post where you knew it was useful, but a huge chunk of code was missing. This is why I always post runnable code, as it helps everyone to understand. Thanks.

@‌ViciousXUSMC, F.Y.I. #include <ButtonConstants.au3> #include <EditConstants.au3> #include <GUIConstantsEx.au3> #include <StaticConstants.au3> #include <WindowsConstants.au3> #Region ### START Koda GUI section ### Form= $Form1 = GUICreate("Form1", 315, 89, 192, 124, -1, $WS_EX_ACCEPTFILES) ;0x00000010 $Input1 = GUICtrlCreateInput("Input1", 40, 32, 121, 21) GUICtrlSetState(-1, $GUI_DROPACCEPTED) ;8 $Label1 = GUICtrlCreateLabel("Drag Here!", 72, 8, 56, 17) ;Do Not Need Button Anylonger ;$Button1 = GUICtrlCreateButton("GO!", 192, 24, 75, 25) GUISetState(@SW_SHOW) #EndRegion ### END Koda GUI section ### ;Loop() ;Func Loop() While 1 $nMsg = GUIGetMsg() Switch $nMsg Case $GUI_EVENT_CLOSE Exit Case $gui_event_dropped ; <--------- instead of reading the input control just monitor the drop event MsgBox(0, "", GUICtrlRead($Input1)) GUICtrlSetData($Input1, "Input1") ;Case $Button1 ;ExitLoop EndSwitch ;If GUICtrlRead($Input1) <> "Input1" Then ExitLoop WEnd ;Action to take on file each time dragged, in this case just a msgbox ;MsgBox(0, "", GUICtrlRead($Input1)) ;GUICtrlSetData($Input1, "Input1") ;Loop() ;EndFunc ;==>Loop kylomas

You state what you want to do, and what you have tried, but not the result. Both of these work just fine for me on WIN7 x64 with the 3.3.12.0 ShellExecute("C:\TestFolder")Run("Explorer.exe C:\TestFolder")If you are receiving a different response, we need more information on the system and version of autoit you're using.

Thanks, I think you really have a cristal ball

sachin3079, Not really. As JohnOne explained, the constants files merely give understandable names to the myriad of numeric constants used inside the Windows API and other AutoIt functions so that they are more easily understood by humans. If you search the forum for "magic numbers" you will see that we constantly recommend the use of these names rather then their numeric equivalents to make the code more readable - which would you prefer to see when looking at the style settings for a combo control after not looking at the code for some months? BitOR($CBS_DROPDOWNLIST, $WS_VSCROLL) 0x00200003 2097155 I know which I would prefer. M23

Have a look in the helpfile to _GDIPlus_ImageResize() and _GDIPlus_ImageSaveToFile()

I think you can find help in this topic and this topic. EDIT: Running script in SciTE4AutoIT you can use: Press Ctrl+Alt+Break to Restart or Ctrl+Break to Stop This message should be visible in SciTE console when you run your script.

Look at the HelpFile for HotKeySet

#include <MsgBoxConstants.au3> MsgBox($MB_SYSTEMMODAL, "Prompt for Chrome automation", "Read post 1 example 5", 10)