Jump to content

MarkSLC

Members
  • Content Count

    49
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MarkSLC

  • Rank
    member
  1. Thanks for your help, aflgenx. I *finally* succeeded, but only after a lot of trial and error (and a bit of cursing) as I tried to figure out how to put all the pieces together. This would make a great tutorial for beginners like me with a bit of fleshing out and going step by step. Thanks again.
  2. I've set up [Prev] and [Next] buttons to move through records in a layout. When the user is at the first record I would like the [Prev] button to turn gray (not disappear) and be non-clickable. Same for the [Next] button when user is at last record. Is this possible? Thx.
  3. Aha! Yes, I was able to trap for it by putting the the 'Get(LastError)' immediately after the print command as you suggest, Wlm Decorte. I had it after an 'End If' and that one line separation caused my problems. Thanks to all.
  4. The FileMaker runtime I've created takes a while to load. In addition, a blank window shows up about 5 seconds before the layout inside the window decides to make its appearance. How can I make some kind of "Loading...please wait" message appear *immediately* to reassure the user that all is well? The message would need to disappear, of course, once the layout pops into view. Thanks.
  5. I have a script that prints a layout without a dialog. But a print progress dialog still shows up (printing 1 of 10, 2 of 10, 3 of 10, etc.) and there is a Cancel button the user can click on to abort the job. How can I trap for the user clicking the Cancel button from this dialog? Thanks.
  6. Thanks Lee and Mel--guess I won't fret about the file size, then.
  7. I have a simple FM project--only about 15 records in one main table with small amounts of text. But when I make the runtime (I'm on a Mac), the .app file it creates is HUGE. Like 40 MB! Is this normal? Makes copying files back and forth for testing purposes a pain. (I've tried the Tools - File Maintenance - Compact & Optimize...) Thanks.
  8. Great sample code, thanks. I can now do what I want using the 'tell front database' 'tell record #' and 'set cell' statements you presented.
  9. Very efficient -- a subscript called at the top of every script. Thanks for the tip, I'll have to use this.
  10. How do you set a field in FM to the value of the AppleScript variable? (Yes, I am aware of the Dictionaries but am too new to make much sense of them.)
  11. From within my FM app as part of a script, I do a 'Perform AppleScript' command. The AppleScript sets a variable, 'set x to 5', let's say. How can I then use the value of that x variable in the FM script that follows the 'Perform AppleScript'? Did a search in the forum on this topic, but did not quite find what I needed. Thanks.
  12. OK. Even though they are the system defaults, I will make it a practice to put abort=off capture=on atop every script just to be sure. Thanks Søren and Mark.
  13. Do you have to put 'Allow User Abort [Off]' and 'Set Error Capture [On]' atop every script? I want these settings to be in effect throughout my app, with every script. I believe they are the system default settings. But after looking at various script examples and doing some tests myself, it seems you may have to keep reissuing them? Can anyone clarify? Thx.
  14. Thanks David and LaRetta. My head is kind of spinning, but you've pointed me in some good directions. Continuing to discuss the layout idea for creating dialogs... 1. What is the trick to making the dialog modal, so that: User clicks button, New Window[] brings up imitation dialog box, user cannot exit or switch to any other window except by clicking one of the buttons in the dialog. 2. How to you deal with/trap/disable the Close/Minimize buttons, should the user decide to click one of those? Thanks.
×
×
  • Create New...

Important Information

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