The trackpad will respond to gestures, much like iOS's version of VoiceOver. In addition, VoiceOver includes features for those that cannot use the mouse, such as keyboard-based navigation.įor users with MacBooks or Magic Trackpads, a number of special multitouch features are also available. VoiceOver also includes support for many Braille displays. Elements also are "interacted" with-for example, interacting with a text box allows reading its text and, if possible, editing it interacting with a scroll bar allows it to be moved using the keyboard. VoiceOver treats the user interface as a hierarchy of elements, which are navigated by various keystrokes. A preview had also been made available for Mac OS X 10.3 Panther, and was titled "Spoken Interface Preview." Kevin Frank on JSON Custom Functions for FM 19.VoiceOver was first introduced in Mac OS X 10.4 and the target was users who had difficulty in reading due to vision impairment, particularly the blind. Peter Beehler on Show/Hide Formatting Bar Mohamed Tawfiq on JSON Custom Functions for FM 19.5, part 2.JSON Custom Functions for FM 19.5, part 1.JSON Custom Functions for FM 19.5, part 2.Well, I have some good news: Bob Gossom of Absolute Advantage has come up with a very clever, and well-documented, self-clearing process lock technique, which I’m pleased to share here with his permission.Ĭontinue reading “Process Lock that Clears Itself” → Tagged Perform Script on Server, Procedure Lock, Process Lock, PSOS Leave a comment Search Search for: Recent Posts A typical drawback to most process locking approaches is that the lock does not automatically clear if the user who locked the process crashes or otherwise bails out of the system abnormally. If you build multi-user business systems, you may have had a need at one time or another to temporarily “lock” a process, so that only one user at a time can perform it. The reporting routine optionally uses PSOS, so you can dive in painlessly and see what you’ve been missing.) Continue reading “Fast Summaries Revisited” → Tagged ExecuteSQL, Fast Summary, FQL, GetSummary, Multi-Find, Perform Script on Server, PSOS 5 Comments Level: Intermediate, Version: FM 12 or later Process Lock that Clears Itself PSOS, host the demo files on FileMaker Server 13 or later. (Also, if you’ve been putting off exploring Perform Script On Server, a.k.a. Bottom line: each of these three techniques can be fastest, depending on circumstances. Or, if you’d rather not do your own benchmarking, scroll down to see results from my tests. Well today we’re going to look at a couple alternatives to Fast Summaries, with the help of some demo files, which you can use to do your own benchmarking. There are various ways to accomplish this, including the Fast Summary technique, which regular readers of this blog may be familiar with, as it has made a number of appearances here over the years. If you do complex data analysis, then from time to time you probably need to group, summarize, and parse data into variables and/or fields. Update : see also Fast Summaries Re-revisited. Continue reading “PSOS – Run Script in File not open Locally” → Tagged Perform Script on Server, PSOS 9 Comments ExecuteSQL, Level: Intermediate, Version: FM 13 or later Fast Summaries Revisited Fortunately there is a “c” option not mentioned above which I’ll get to shortly, but first let’s demonstrate the issue. Hmmm… I think we can agree that from a security standpoint “b” is a non-starter, and the whole point of this article is to avoid “a”. …in other words, if you want PSOS to be able to access files, you need to either a) already have the files open client side, or b) throw caution to the wind, and configure the hosted files to auto-open with pre-entered credentials. If we consult the online help entry for running scripts on server, the official word is that server-side scripts can access other FileMaker files only when… But of course there may be circumstances where you’d like to be able to access files server side that the user does not have open client side, either because the user’s credentials do not allow access to those files, or because you’d rather not have to open the files client side merely to facilitate a PSOS call. Here’s the behavior, or misconception, actually: a server side script initiated via PSOS (apparently) cannot access files on the server unless the user already has those files open locally. Today I want to take a look at a certain Perform Script On Server (PSOS) behavior, and for those who find this behavior to be inconvenient, propose a work around. Update: See Jason Wood’s suggestion in the comments section for making this technique more secure.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |