Macro Scheduler 15.0.25 released

[Dorian (MJT support)]

We have just released Macro Scheduler 15.0.25

For more details please see the Version History Page or this Blog post.

[Grovkillen]

Thanks!

[Grovkillen]

I got PDF XChange installed and when I load a local pdf for the tMSWebBrowser object (URL property) the PDF-XChange interface is showing up. Pretty great if you ask me

Not sure if this part of the scoop?

The Acrobat Reader object seems to work too but I'm hoping to use SumatraPDF instead, not sure if that will work but will keep hacking.

EDIT:
The PDF XChange app have included a "Plug-In for MS IE".

[Grovkillen]

Code: Select all

Dialog>Dialog1
object Dialog1: TForm
  Left = 641
  Top = 288
  HelpContext = 5000
  BorderIcons = [biSystemMenu]
  Caption = 'CustomDialog'
  ClientHeight = 365
  ClientWidth = 594
  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
  DesignSize = (
    594
    365)
  PixelsPerInch = 96
  TextHeight = 13
  object MSWebBrowser1: tMSWebBrowser
    Left = 10
    Top = 7
    Width = 567
    Height = 346
    Anchors = [akLeft, akTop, akRight, akBottom]
    TabOrder = 0
    ControlData = {
      4C0000009A3A0000C32300000000000000000000000000000000000000000000
      000000004C000000000000000000000001000000E0D057007335CF11AE690800
      2B2E12620A000000000000004C0000000114020000000000C000000000000046
      8000000000000000000000000000000000000000000000000000000000000000
      00000000000000000100000000000000000000000000000000000000}
  end
end
EndDialog>Dialog1

//SetDialogProperty>Dialog1,MSWebBrowser1,URL,C:\Users\jimmy\Downloads\test.pdf
SetDialogProperty>Dialog1,MSWebBrowser1,URL,https://www.chartjs.org/docs/2.6.0/charts/line.html
Show>Dialog1,r

Looks beautiful!

[Grovkillen]

Some feedback. I will edit this post if I find more.

RegisterAsDropTarget should be default set to false since it will (probably) mess up stuff if it happens unintentionally.

Code: Select all

SetDialogProperty>Dialog1,MSWebBrowser1,RegisterAsDropTarget,False

GetWindowChildList is now part of the gutter but missing in the "Code Builders" panel (or am I really blind?).

I know the new dialog objects are experimental but shouldn't we be able to act on things that happens within those objects? The tMSHTMLViewer is great and "only a little change" would make it a super object in terms of creating forms, the new browser object seems much more powerful but at the same time hard to act on. I'm just writing stuff from the top of my mind here

[Grovkillen]

The PDF object kinda grows on me. I can really see it in use to make popups showing the PDF without any status bar etc. Good job on that one! If we can act on events inside it (like click and select etc.) it would be really powerful.

The link in the blog post is incorrect by the way. https://get.adobe.com/reader/

And, perhaps we could have a command to be able to check if Adobe Reader is installed?

[Marcus Tettmar]

I got PDF XChange installed and when I load a local pdf for the tMSWebBrowser object (URL property) the PDF-XChange interface is showing up. Pretty great if you ask me

Not sure if this part of the scoop?

All depends how your system is configured, what IE plugins you have and how they are configured and whether they are enabled for the embedded IE control. All totally, fully, utterly, completely and massively beyond our control and responsibility ... HOWEVER - one of the reasons for adding the web browser control was precisely because of the possibility of being able to use it to preview PDFs. When that request was made it occurred to me that a web browser could be used to do that **IF** so configured and **IF** the appropriate plugins exist.

[Grovkillen]

Got you!

Sounds like a great approach and very powerful given the way you describe it.

[Marcus Tettmar]

GetWindowChildList is now part of the gutter but missing in the "Code Builders" panel (or am I really blind?).

It is there, defined in comdef.ini but we don't overwrite your comdef.ini on upgrades as you may have favourites etc set up.

I know the new dialog objects are experimental but shouldn't we be able to act on things that happens within those objects?

You can try some of the events and see if they work - but they may require types which are not compatible.

The tMSHTMLViewer is great and "only a little change" would make it a super object in terms of creating forms, the new browser object seems much more powerful but at the same time hard to act on. I'm just writing stuff from the top of my mind here

There are no plans to do this and probably beyond the capabilities. Note the name includes the word *Viewer*. It's not intended as a way to create forms. You can do that already.

[Grovkillen]

The tMSHTMLViewer is great and "only a little change" would make it a super object in terms of creating forms, the new browser object seems much more powerful but at the same time hard to act on. I'm just writing stuff from the top of my mind here

There are no plans to do this and probably beyond the capabilities. Note the name includes the word *Viewer*. It's not intended as a way to create forms. You can do that already.

But it seems to already be implemented except it doesn't add the forms data. See my thread here: viewtopic.php?f=1&t=11314#p48742

The "Results" variable isn't populated as expected (that would be a string with "name=value" pairs).

[Marcus Tettmar]

The "Results" variable isn't populated as expected (that would be a string with "name=value" pairs).

So that actually has nothing to do with the HTML viewer object and is in fact because the parameter type of the Results parameter is a string list which Macro Scheduler doesn't know about. However, just for you, we have just deployed an update which now copes with this and converts it into an array. Version 15.0.27.

[Grovkillen]

Woohoo! You're the greatest Marcus! I know I bug the day out of you but you do like me just a little bit I can tell

[mhcha]

Version 15.0.27. I appreciate that the update allows me to use The HTMLViewer as Form to get a Submit response.
It's a really good feature!

I'm using Grovkillen's example.
I hope the post below will be helpful to others as well.
viewtopic.php?f=1&t=11314