If I have some favorite script steps and I click on that script step outside of the favorites, I’ve got a blue star, indicating it’s part of my favorites. The icons have been updated to better represent the kind of compatibility we are looking for at the moment. It makes more sense in 15, the picture as well as the script compatibility. This button, next to the “gather data” tab changed. We have another tab that is just some general preferences about the script workspace. This includes the syntax coloring that was part of FileMaker 14. We have a new script workspace preferences. Obviously, with a hundred-character script name limit, we’re not going to need to get that large. But, now in 15, we can make it as large or as small as we need to. In FileMaker 14, the panel on the Mac OS side was limited to a smaller size. The first one that people will find very useful is the expanded script named panel. The second feature of FileMaker 15’s updated script workspace just includes some general UI tweaks. It’s bringing up an empty red space that points to an error. And, when I’m debugging a script, I will not see this highlighting either in the debugger. If I attach this to one of those error-filled scripts and then look at it in the edits area, I do see some red here, but I don’t see the highlighting of error color coding conditions. When we are working with scripts in a button, we do not have this option of being able to see the errors. As soon as I fix the error, the problem goes away the highlighting goes away. ![]() So, I would have to check for problems again to identify those errors. This one, even though it is in red, it’s not highlighted like it was. But, if I were to close the script workspace and then reopen the workspace, I would find that the error highlighting has gone away. ![]() Now, this error highlighting is available when I have a script workspace open. I could go through each one of them and I can fix them. It’s very easy as I scan through my script to find all of the errors.Īnd, again, if you look at the scroll bar, you can see that there are red indicators throughout the scrollbar, pointing me to the approximate location where the error occurs. Notice that the errors are already highlighted. When I click “OK,” FileMaker script workspace will open up all four of these scripts into separate tabs and allow me to go through and fix them. You can see that it has caused 174 errors in my import summary. I’ve imported four scripts from another solution. The second way that we can check for problems is by importing scripts. I’m going to just change it to any old field there, and you notice that the error highlighting has been removed. So, I have an error here, and I can simply go and fix it. This is telling me the approximate location that the error is in my script. That is very useful for long scripts that contain multiple errors. Notice over in the scroll bar, there is a little red indicator. It has highlighted the script step in a color of my choosing, and it has highlighted the parameter that is causing the error. I’m going to right-click on it and choose “Check for Problems.” This scans each line of the script and finds the errors. I’m going to go click on the name of the script. In this script, I have an error, but it’s not very visible. It allows more experienced developers to find script steps easily without resorting to other tools. Its purpose is to allow beginner developers to see the script steps that could cause errors. The first feature, error color coding conditions, allows us to find the errors in a script. We’ll look at specific enhancements for each as well as a few things to watch out for. Then we’ll look at some general tweaks that they’ve made and at the much-requested undo and redo feature. We’ll take a look at the error color coding conditions. There are a lot of features that have been added. ![]() In just one year, it has undergone some great changes. The script workspace was introduced in FileMaker 14. In this video, we’re going to take a look at FileMaker 15’s updated script workspace. Hello, my name is Jeremy Brown and I am with Soliant Consulting. We will look at these features as well as some things to watch out for as you use them. ![]() In this video, Jeremy Brown explores the error color coding conditions, general UI tweaks, and the much-requested undo/redo feature. The newly improved script workspace in FileMaker 15 comes with some great enhancements.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |