I thought it was about time for an update.
We are currently working on improving Macro Scheduler’s UI appearance under 4k UHD monitors. These screens are becoming more common, especially since the launch of Windows 10 which includes improved scaling features.
Macro Scheduler needs to be DPI aware in order to perform image recognition on modern high definition screens. The problem is that when you make an app DPI aware, Windows then doesn’t automatically scale it for you. The upshot of this is that the 16×16 toolbar icons amongst other things are then almost too small to see. Some older visual components also don’t cope well.
So we are working hard creating new 32×32 icons and making tweaks to some of the forms and components to ensure Macro Scheduler looks good and is usable on this new breed of high-res monitors.
We also continue to work on script engine improvements and feature suggestions. However, right now we are prioritising the UI improvements and since more and more people are using new 4k screens we plan to release an update with only these UI changes before releasing other changes. This will allow us to get this out more quickly.
Watch this space.
Every now and then someone asks something like “How do I change the font in a modal dialog box?” or “Can I make an Input box multi-line?”.
Well, no, you can’t do those things to the standard Message/MessageModal or Input box functions. But, don’t forget that with Macro Scheduler you have the ability to create your own dialogs and make them act and feel pretty much any way you like. So the answer to the above questions, is “Create your own versions”.
As an example, let’s say you want a modal dialog that looks and acts much like the standard modal message box created by MessageModal. Only you want the text to be green in an italicized aerial font. Here you go:
//this would go at the top - customize as you wish Dialog>CustomMsgBox object CustomMsgBox: TForm Left = 493 Top = 208 HelpContext = 5000 BorderIcons = [biSystemMenu] BorderStyle = bsSingle Caption = 'My Message' ClientHeight = 170 ClientWidth = 319 Color = clBtnFace Font.Charset = DEFAULT_CHARSET Font.Color = clWindowText Font.Height = -11 Font.Name = 'MS Sans Serif' Font.Style =  OldCreateOrder = True ShowHint = True OnTaskBar = False PixelsPerInch = 96 TextHeight = 13 object MSMemo1: tMSMemo Left = 0 Top = 0 Width = 321 Height = 137 Font.Charset = ANSI_CHARSET Font.Color = clGreen Font.Height = -11 Font.Name = 'Arial' Font.Style = [fsBold, fsItalic] ParentFont = False TabOrder = 0 end object MSButton1: tMSButton Left = 121 Top = 143 Width = 75 Height = 25 Caption = 'OK' DoubleBuffered = True ModalResult = 2 ParentDoubleBuffered = False TabOrder = 1 DoBrowse = False BrowseStyle = fbOpen end end EndDialog>CustomMsgBox SRT>ShowMsg SetDialogProperty>CustomMsgBox,,Position,poScreenCenter SetDialogProperty>CustomMsgBox,MSMemo1,Text,ShowMsg_Var_1 Show>CustomMsgBox,r END>ShowMsg //do this to call your message Let>MyMsg=Hello world, this is a lovely custom message box GoSub>ShowMsg,MyMsg
And don’t forget that once created you can call the dialog any time you like. And if you want to use it in lots of scripts then put the dialog block and subroutine into an include file and use Include> at the top of each script you want to use it in.
I’ve only just discovered that our newsletter subscriptions system has been broken since last January! New customers and anyone signing up to our newsletter since 15th January 2015 were not correctly subscribed to our newsletter. Luckily we have the email addresses in our database, they just weren’t allocated to the correct list. I’ve now fixed this and moved affected email addresses to the correct list. So those affected will now start receiving our newsletters. Hopefully you won’t be too surprised when you start receiving newsletters from us.
You may already be familiar with the Macro Scheduler debugger and know how to set code breakpoints. But did you know you can set variable breakpoints too? With a variable breakpoint you can cause execution to pause when a specified variable becomes equal to a given value.
You will find the “Variable Breakpoints” option under the “Debug” menu in the code editor.
You can set one or more variables and values. Then at any point during execution when one of those conditions occurs the macro will pause and allow you to debug.
This can be very useful when you are not sure where an issue is occurring but you may know that a specific set of data causes a problem that you want to debug.
So it’s Black Friday. Sounds so gloomy. A day where many appear to go mad and gorge.
There’ll be no extra discounts from us today, but what we will do is donate 10% of today’s sales to The Woodland Trust and St Mungo’s charity for the homeless.
So if you buy or upgrade Macro Scheduler today, or renew your maintenance you’ll be planting some much needed trees and providing for people who really need stuff.
In this video I demonstrate how to use IE’s F12 key to invoke Developer Tools and use that to quickly find the elements we’re interested in and the attributes we need to use:
(You might want to click on the video toolbar to select a larger resolution size, view full screen or view on YouTube so that you can see the code).