Guys,

Hoping someone can help me out with this question.

When you use the pause script, in scriptmaker, the left hand FileMaker Status bar comes up with two buttons continue or cancel. Can I replicate the continue button within my layout using a script within scriptmaker, as I want to get rid of the FileMaker status bar.

Thanks Guys

Jalz

Hi -

Check this thread

http://www.fmforums.com/threads/showflat.php?Cat=&Board=UBB45&Number=84938&Forum=All_Forums&Words=&Match=Entire%20Phrase&Searchpage=0&Limit=25&Old=1day&Main=84932&Search=true#Post84938

Thanks Andy,

Geat help, does the business in browse mode, however in preview mode, I cant seem to activate the button. Is there a way around this?

Cheers

Jalz

Hello Jalz,

You're right, scripted buttons don't work a layout that is in preview mode.

There are a few ways around that problem. One of them which may be of interest to you is the subject of a demo which can be downloaded from:

http://www.nightwing.com.au/FileMaker/demos1.html#d2

It shows a method for providing users with a floating 'navigation palette' in preview mode.

Instead of using "Pause/Resume Script" in the script use the "Enter Preview Mode [pause]" step.

This isn't to say that Ray's floating palette isn't going to meet your needs, just that you may need something a bit simpler.

Hi Vaughan,

Well, I'm all for simplicity...

But I was not aware (and still am not... ) that using the "Enter Preview Mode [pause]" command in place "Pause/Resume Script" causes layout buttons to become active/clickable in preview mode?!!

Perhaps you could clarify what you had in mind?...

Another way to approach this is with the following steps:

- enter preview mode

- do a 'copy all records'

- enter browse mode

- paste into a global container field

Then you can see your preview in browse mode and have as much buttons as you want...

Hope this helps,

Ernst.

Hi Ernst,

There is a technique which goes back to the early nineties - which is what I assume you are referring to - by which a preview image can be captured and placed into a container. However it will not work using the 'Copy All Records' script command.

Instead it can be achieved using the standard 'Copy[ ]' script step from among the editing commands. The technique is one that has been around for many years, and was widely publicised by Dana Alan Perry of DataDesigns, back around 1996. Her .fp3 demo of the technique is still available online at:

http://www.datadesigns.com/tips/tips_1.htm

The technique is simple to implement if you are only ever going to need to preview a single page, always at the same orientation and only ever at 100% magnification. But then, operating within similar constraints (eg providing only a single button to cancel preview) a floating pallette is also very simple to implement.

Using either technique, it's possible to provide controls for zoom, preview, alternate orientations, scrolling and multi-page navigation. But when these are included, either technique becomes more challenging and time consuming to implement. The palette demo I referred to previously is somewhere in the mid-range in terms of features and complexity - enough to get the 'feel' of the technique, but by no means exhaustive.

Both techniques have their advantages and disadvantages and which is best depends on the context.

Hi Ray,

You're totally correct; it's just a 'Copy' step, so not 'Copy all Records'.

Personally I like it a little bit more then the floating palette method, because

- everything takes place in one window

- there is no need to have the user paused in a script

But I do not doubt that there are also good reasons to take the palette approach.

Absolute truth is rare. Or something like that...

Regards,

Ernst.

Ray -- I was under the impression that he wanted the Continue button on the status area to be active, not buttons on a layout.

Brain fade.

Oh - OK Vaughan...

After over 3,000 posts I guess you're entitled to the occasional 'mesmerised moment'!

Ray -- yes, there's been more than a couple of dud posts over the years.