Jump to content

John Kornhaus

Members
  • Posts

    11
  • Joined

  • Last visited

John Kornhaus's Achievements

Rookie

Rookie (2/14)

  • First Post
  • Collaborator
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

  1. Check the documentation that came with your scanner. Many of them can be configured to prefix or postfix the scanned data with a string of characters, including control characters. You will probably need to scan in a special code from the manual that will program the scanner to first send a ctrl-number sequence followed by the characters from the barcode.
  2. FM wants to update the portal record twice when created in a portal, re-evaluating the auto-enter calcs and re-triggering scripts. To work around this, you need to temporarily disable the script triggers after the first update to prevent the second update from re-triggering the script. Change your script trigger to something like: Field & Left( zippScript_PerformScript( Get( FileName ); "MyScript"; "MyParams" ) & zippScript_DisableTriggers; 0 ) Add this to the end of the triggered script: Set Variable[$Result; zippScript_EnableTriggers] The first update to the portal record will now trigger the script and then turn off any further triggers. The second update will then re-evaluate the auto-enter calc but will not cause a second script to be triggered. At the first opportunity (after the updates have been completed), FM will run the script and the triggers will be turned back on, awaiting the next change by the user. John
  3. San Antonio, TX–July 19, 2007 zippTools is pleased to announce the release of a Mac Universal Binary shell scripting plug-in, zippShell 1.1. It is available for immediate download from our new web site, http://www.zipptools.com. What is zippShell? zippShell is a plug-in for FileMaker Pro® that allows developers to harness the full power of the operating system by executing shell scripting commands from within any calculation dialog. With zippShell you can: • Perform file-manipulation functions • Perform complex text processing with grep or perl • Send and receive files from FTP sites and Web Servers • Return the result of a shell script from a calculation • Schedule a shell script to be performed at a specific date and time ... and much more. System Requirements FileMaker Pro 7 and later; Mac OS X (PPC) or Mac OS X (Intel). zippShell is provided free of charge to the FileMaker community. See the license information included in the example file for further details. Contact John Kornhaus info@zipptools.com www.zipptools.com
  4. Certainly. There are complete instructions in the example file included with the plugin. Basically, you call the _Version() function and interpret an invalid response as a missing plug-in. You can use the auto-update feature to download updated plug-ins from the server to a client machine. It takes a bit of work on your part, but it can really pay off if you have many clients or frequent plug-in updates. See the FMServer documentation for details. Many thanks to everyone supporting all the free plug-in developers.
  5. I would like all of my plug-ins to be cross-platform, if possible. I'll look into it if there is enough interest.
  6. Hi djbeta, I'm glad you like zippScript. Make sure you get the just-released v2.2, available now from its new home at http://www.zipptools.com. Keep an eye on this site, I have a backlog of free plug-ins and tools I'll be releasing as quickly as I can finish the documentation.
  7. San Antonio, TX–July 12, 2007 zippTools is pleased to announce an update to the premier free script-triggering and script-scheduling tool, zippScript v2.2. It is available for immediate download from our new web site, http://www.zipptools.com. What is zippScript? zippScript is a plug-in for FileMaker Pro® that adds easy yet powerful event-based tools to your programming toolbox. Simply add a zippScript trigger in a calculation dialog to: - Perform a script when a field is modified - Perform a script when a record is committed - Perform a script when a field is displayed - Perform a script when the mouse is over a field (FM8 and later) - Call a script with a calculated name - Schedule a script to be performed at a specific date and time ... and much more! New in version 2.2 - Perform a script after a specified period of no user activity System Requirements FileMaker Pro 7 and later; Mac OS X (PPC), Mac OS X (Intel) or Windows. zippScript is provided free of charge to the FileMaker community. See the license information included in the example file for further details. Contact John Kornhaus info@zipptools.com www.zipptools.com
  8. There's a bit more to it that just turning on the auto-update option in both the client and server. Plug-ins can be checked and downloaded on demand from a file that uses them, but it is up to the developer to write the script to do this. Check the electronic documentation on the Server 8 CD. You should find answers to most of your questions in the AutoUpdate.pdf file. I have included a pre-TAR'd copy of the plugin in the zippScript 2.0 package to help developers running a Mac OS X server. John
  9. Hi, sorry I'm late to the party.... I don't visit here often and just ran across this question. FileMaker will respond differently to requests to run a script depending on what it is doing at the moment. If it is doing something, there is nothing in the plug-in API that will let you break into that processing and force it to do something else (I consider this A Good Thing™). Requests to perform a script are queued and executed at the next opportunity. If the requests are made while in the midst of running a script, then the next opportunity will come when the script has finished executing. If a request is made while FM is idling and waiting for the user to do something (no script is running, or a script is paused), then the new script can be executed immediately. Soren's comparison to an AppleScript'ed loop is not really relevant here since he's already circumvented FileMaker's script scheduling by implementing the looping structure outside of FileMaker and simply making calls to the sub-script(s) as necessary. The subscripts will run properly interspersed with the control loop since FileMaker is idling and waiting for some incoming commands. The same problem occurs in all three plug-ins mentioned here, because we're all using the same function call in the plug-in API to request a script to be run. We're all bound by the same limitations in how FM will honor that request. But, there are some tricks we can use to work inside the execution framework that FM provides, and I think we can solve this problem with a little out-of-the-box thinking. If we examine the problem, we'll see that the reason the sub-scripts are grouped after the control loop is that the request to run the script occurs while FileMaker is busy, namely running the control loop that is trying to call the sub-script. If we can delay making this request to some point when FM is not busy, say while it is paused, then we can trick FM into running the sub-script right away. This is exceptionally easy to do in zippScript 2.0 by calling zippScript_ScheduleScript( Get( CurrentTime ); Get( FileName ); "ScriptName" ) The next time FM has time available, the schedule will be activated since the scheduled time has already arrived and the sub-script will be called. Since by definition FM isn't doing anything then, the script will run immediately rather than being deferred. We can force FM to make some time available to plug-ins by inserting a Pause/Resume script step right after the call to schedule the script. If you now try to run the looping script, you'll find that FM will pause indefinitely after running the sub-script (requiring a click on the "continue" button, or a press of the "enter" key), regardless of the delay you specified in the script step. I believe this is a bug and will report it, please do the same if you'd like to see this fixed in a future FM update. This, too can be worked around by scheduling the script so that it will resume any paused script when it is executed. This fix required a slight change in the parameter list for the _ScheduleScript function; I have a beta of zippScript 2.0.1 available (Mac only at the moment) if anyone would like to test it. Email me, jkornhaus AT mac.com. The final version with some updated docs and new examples will be available at http://homepage.mac.com/jkornhaus/filemaker/ in a few weeks. John
  10. To extract the characters from an fmx::Text object, use the GetBytes() or GetUnicode() functions.
  11. zippScript 2.0 is now available for download. zippScript 2.0 adds powerful script triggering and script scheduling tools to your programming toolbox. With this plug-in you can: • Perform a script when a field is modified • Perform a script when a record is committed • Perform a script when a field is displayed • Perform a script when the mouse is over a field (FM8 and later) • Schedule a script to be performed at some future time • Call a script with a calculated name ... and much more. The original zippScript was one of the first FileMaker® Pro 7-native plug-ins to be released and the first free script-triggering plug-in to provide the critical ability of passing a parameter string to the triggered script. zippScript 2.0 builds on this solid foundation by adding the ability to schedule a script to be triggered at some future time and adding functions to temporarily disable script triggering while performing scripted record updates. zippScript 2.0 is compatible with FileMaker Pro 7 and later, and will run natively on Mac OS X (PPC), Mac OS X (Intel) and Windows. It is a drop-in replacement and upgrade for zippScript 1.1. This plug-in is provided free of charge to the FileMaker community. zippScript 2.0 is available for download from http://homepage.mac.com/jkornhaus/filemaker/
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.