Hello,
in this thread I want to post to you what's new in development of MBS Plugin, version 14.4.
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.
You can click on the mbs-plugin-development tag and subscribe to get an email for new topics with this tag, so you get notified.
Greetings
Christian
@MonkeybreadSoftware
To what extent is the plugin capable of modifying the Field Definition view (if any) ?
It would be great to have some tools in here to help easily identify fields with broken references or missing fields in them (errors in other words) to address them, either by way of sorting, a filter, or colouring fields as such.
(Edit: Oh I see I could do a search using the find tool for "missing" which gets me what I'm after, nevermind!)
1 Like
Thanks for helping yourself.
We could of course think about highlighting here, too.
@MonkeybreadSoftware
Would you be willing to make the plug-in treat Insert Calculated Result
and Insert Text
as variable declarations?
I sometimes use these for variable initialization and usually have to add a var declaration comment above to satisfy the variable name checker.
Or perhaps they only count as declaration/initialization if the "Select" checkbox is checked?
Thanks!
That is 14.3?
I thought we had that built in already.
Otherwise I can check and you can use comment line
# @variable $myvar
To tell the plugin about it.
1 Like
Whoops! You're right I guess i was still using 14.2! I just updated to the prerelease and it works exactly how I was hoping (even without the # @var $myvar
comment). Thanks Christian!
1 Like
Hey Christian,
The new SyntaxColoring.AutoCompleteVariables.GetGlobals
feature is really cool. Would it be possible to get it for local $variables too? Our system uses both custom functions and some boilerplate Let() calcs to populate known local variables that always have the same name and act as reserved words in our system.
E.g. $error
, $sqlQuery
, $sqlParameter1/2/3
If we could declare a set of "known local variables" somewhere that would save me having to write declaration comments for those variables in every script.
Thanks as always for all your work.
J
You like to have some local variables always show up?
Wouldn't it be better to just write a comment for them in the script?
e.g. on top of a script:
# this script uses the following local and global variables:
# @variable $Param, $$UserID, $$LoginTime
That's what we do now but certain variables show up in almost every script, like $error.
Okay, let me add you a SyntaxColoring.AutoCompleteVariables.SetLocals function. I hope it helps.
2 Likes
That looks perfect, excited to try it!
Searching list of table occurrences.
We have beautiful way to search the fields but in a large system with many interconnect TO that pop-up menu can get very long there is no way to type ahead to find anything in this menu.
is there any possibility to be able to search this menu object.
1 Like
MacOS has the feature, that when you click on the popup menu, you can type and it jumps to next matching entry.
It doesn't seem to work for me I may be on Estimates and want to go to invoices_x I type "I" and it jumps to the first "I" with naming conventions I can't seem to get to invoice_x I have to then down arrow dozens of time to get to it.
I would like to have a way to search get back some list that contain only invoice if that is what I typed then from that list filter further and then use your cool little way to jump to that TO (that usually appears in top right for last chosen TO )