So to answer your question, there is no “Set Object Attribute” script step (yet). Keep sending it to FileMaker’s feature request page, perhaps we will have it with the next version.
Still, have fun with your new FileMaker.

I just used FM Pro Advanced 11 but can’t find “Set Object Attribute” script step. Where did you guys see that?

Now I did further testing, recreating your results with less than full-height windows. See my new finding in the addendum in my post.

I do not the problems with the Inspector. I have only one Inspector window open, switching with Cmd+1/Cmd+2/Cmd+3 with my left hand between the three tab pages. That works fine on my 15″ MacBook Pro.

For the other remarks, FileMaker Pro 11 is out less than a week. I try to emphasize positive things, waiting a couple of days before I post a bad feature list. But, hey – perhaps I can work on a new April Fool’s joke.

Moving lines in list : is indeed easier but putting a line at the first place is much more difficult. If you move too far, even a few mm, the line doesn’t move at all.

Also a step backwards is the layout of the import window, the one you use to match fields. You can hardly see the difference between the arrow and the … This will be a cause of many mistakes, i guess.

For screens smaller than 30inch and an AZRTY (or alike) keyboard without numeric pad, showing and hiding a specific inspector doesn’t work with the shortcut’s. It takes longer than before to change the most common things, like borders, pop-up menu’s, …

But generally, I love v11!

Take a look at the ‘raphaeljs’ website.

Also, have a look at the Fusion Reactor plugin for FileMaker. It enables you to do loads of cool things like display images from a container field in a web viewer, and run scripts, calculations or update fields from within your JavaScript code. Pretty neat stuff. It also lets you create your own drop in functions which can do all that stuff your own way! Its got pretty good documentation too.

Using this, you could just provide a script which handles the basic functionaly, and a table with a record for each button. Each button record could have two containers, one for an active image, and one for an inactive version. It can also have three text fields – the first to give the button a label, a second to name a script to run when you click that button, and the other for an optional parameter to pass to that script.

Then, users would only need to import that table, and your script to get the whole thing working, and they could easily add their own buttons, or change the button images to theme it. Pretty cool!

I am new to filemaker, but I have to develop a database for my company.
I’d like to hide the filemaker toolbar and use yours instead. My problem is that I’d like to add two buttons in the find mode, to include or exclude records but I don’t really understand how to do it because I do not know anything about HTML code!
Is there any chance you could explain how to do that? It would be really helpful, and kind!

Sophie

PS: I hope my vocabulary is ok, I’m French and I’m using a french version of filemaker…

First of all, I use a custom function written by Mikhail Edoshin, BitIsSet( Number, Bit ).

// Returns whether or not the binary bit in the given number is turned on. i.e., ~BitIsSet( 16; 5 ) would return True as 16 is 10000 in
// binary. Similarly, ~BitIsSet( 18; 2 ) would also return True as 18 is 10010 in binary. This calculation is thanks to Mikhail Edoshin
// and is found at http://edoshin.skeletonkey.com/2005/11/custom_function.html.
//
// Written by Mikhail Edoshin

Mod( Div( Number; 2 ^ ( Bit – 1 ) ); 2 )

Next I have a set of custom functions that are simply constants, such as kModifierShift:

// Used as a named constant. Should have a value such that ModifierKeyIsActive( kModifierShift ) = True when the shift key is held down.

1

kModifierCapsLock is 2, kModifierControl is 3, etc, each value corresponding to the bit tha

t’s true from GetActiveModifierKeys.

Finally, I have ModifierKeyIsActive( ModifierKey ), which accepts one of those constant custom functions:

// The ModifierKey parameter should be an integer between 1 and 5. These can be accessed via the kModifier* custom function
// constants. Returns whether or not the given modifier key, as specified by it’s power of two equivalent, is held down at the time
// the function is evaluated.
//
// EXTERNAL REQUIREMENTS: The BitIsSet custom function. Easiest to use with the presence of the kModifier* custom function
// constants.
//
// Written by Charles Ross

BitIsSet( Get( ActiveModifierKeys ); ModifierKey )

With the above, I get code that looks quite nice: If[ ModifierKeyIsActive( kModifierShift )]