MBS FileMaker Plugin 15.3 development

Hello,

in this thread I want to post to you what's new in development of MBS Plugin, version 15.3.

Download is available as usual here:

monkeybreadsoftware.com/filemaker/files/Prerelease/

If you like our plugin, bookmark, like or forward this thread.

If not, well you can ignore it.

New functions in documentation.

Thanks for supporting our plugin.

For questions please do not answer here, but start a new discussion.

Greetings
Christian

15.3pr1:

2 Likes
Fixed a crash with variable check if your line length is over 5 million characters.

I'd like to know who submitted that one lol !

1 Like

Certainly not on an 8-bit computer !

Some languages don't bother with LF, you may type a lot of things on a single line :wink:.

Sounds like a runaway iteration loop.

15.3pr2:

15.3pr3:

  • Updated DynaPDF to version 4.0.102.288.
  • Added DynaPDF.SetActiveSigField function.
  • Added SystemInfo.isTahoe function.
  • Fixed a problem in CompressFiles method for ZipMBS class, broken since 25.0.
  • Improved SQL.InternalSQLiteLibrary.Dump function.
  • Updated SQLite to version 3.50.1.
  • Improved our CoreML functions to handle Int8 data type in addition to Float16, Float32, Int32 and Float64 data types that your models may use.
  • Updated CURL library to version 8.14.1.
  • Added CURL.SetOptionSSLSignatureAlgorithms function.
  • Improved loading LDAP library on Linux to work on Ubuntu 22 and 24.
  • Changed copy text/selection in ScriptWorkspace to indent the lines.
  • Added SelectedOnly and EndOfLine parameters for ScriptWorkspace.StyledScriptText function.

Feature request, this one came from Kent at fmslug but is something I also struggle with greatly.

On mac, the script debugger has an annoying trait where if you step over perform script steps, it jumps to the bottom of the debugger so you can't see what is coming next. Can this be fixed via MBS in any way so that it always ensures you can see the next 5 or 6 lines of a script coming next?

You mean to scroll the debugger automatically and make sure at least the next three lines before and after are visible?
I think I could do that.

2 Likes

Yes that's the one :+1:

15.3pr4:

  • Updated mongo-c-driver to version 1.30.5.
  • Improved OCR error messages to state whether tesseract or leptonica library is not loaded.
  • Added search: prefix for comment links to jump to whatever text you provide.
  • Added SystemInfo.AppResourceUsageStatistics function.
  • Improved how we scroll lists to make sure more rows below and after a visible.
  • Improved debugger in FileMaker to scroll better and show a few rows adhead on stepping.
  • Improved our CopyButton to not show the warning in console about adding a button to the title bar.
  • Updated DynaPDF to version 4.0.102.290.
2 Likes

This feature has unintended problems in the Script Workspace.

Please install an older version if you are affected by this bug.

You can find a newer build here: builds folder

1 Like

15.3pr5:

15.3pr6:

  • Updated Saxon library to version 12.8. Download
  • Added a search button to find function on documentation website.
  • Changed findbar to appear automatically in database design dialog if you use it there frequently.

15.3pr7:

  • Added Files.PrintFile function for macOS and Windows.
  • Rewrote macOS part of Files.LaunchFile to use newer API on macOS 10.15 or higher.
  • Updated DynaPDF to version 4.0.102.291.

And released:

MBS Plugin 15.3 for Claris FileMaker

1 Like

This request is obviously a little too late for 15.3 but hopefully this is doable for the next version!

This has always been an annoying thing for me with the Field calculation dialog pictured.

When you want to change the context of the calculation (which is often when working with an Interface table), you change it via the drop-down at the top. The problem is that the current table occurrence on the left does not change. You always have to change this context to be the same as the one you just chose at the top and this is super frustrating.

Is there any way possible that these two can basically be in sync so that when the top context changes, the 'current table' automatically changes to be the same one? There really is no reason for these two to ever be different upon changing of the evaluation context.

I would be eternally grateful!

But why don't you have it set to current type?
Which should be the same as above.

Sorry not sure I follow.

Here is an example. I have an interface table in my file. In this type of solution, all layouts are based on an anchor TO which is based on the interface table. However I have many interface table occurrences.

When you create a new calculation, the default TO it evaluates from is always the very first TO that got created in the file. In my case, D_Interface

I never want to create calcs evaluated from that context. For me the calculations are always evaluated from the context of wherever that calc is used, such as the layout (and thus the relevant TO).

So, imagine I'm creating a new calculation:

By default, the context is set to D_Interface. "Current Table" by default also always gets set to D_Interface.

Now I want to choose the actual correct context for this calculation. I must now select the correct context from the drop-down.

When I set the evaluation context, the left hand side field listing does not update the "current table" TO.

I can't just begin adding fields to this calc, as it then adds them for the wrong context. I must first now go and change the TO on the left to the one at the top before i can start writing the calc.

You have to do this every single time in this case, and it's always the same TO I need to change on the left, and it always gets changed to "Current Table" for the newly selected evaluation context.

I have never understood why when you change a calculations evaluation context can't the current table TO on the left also automatically change. The left hand side is purely for field selection it has no effect on the calculation at all, but it is just a complete nuisance to have to now always change this before I can start building the calc.

hope that clears it up !