SPONSORS:






User Tag List

Results 1 to 5 of 5

Thread: Appstate (s)

  1. #1
    Junior Member
    Join Date
    Jun 2001
    Location
    Milford
    Posts
    27
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Appstate (s)

    Ok i have created a brand new Plan, Script, and Frame file. Inside the frame I have put the appstate. And i get an error.


    Function USRAppstate not defined?

    Can anyone help? It seems as though the script doesn't see the frame. I also tried to add a use statement.



    ------------------

  2. #2
    Senior Member
    Join Date
    Aug 2000
    Posts
    192
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Appstate (s)

    do you receive the compile error in the frame file or the script file?

    ------------------

  3. #3
    Junior Member
    Join Date
    Jun 2001
    Location
    Milford
    Posts
    27
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Appstate (s)

    the script file

    ------------------

  4. #4
    Junior Member
    Join Date
    Jun 2001
    Location
    Milford
    Posts
    27
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Appstate (s)

    ok i got it to work bu i had to use a use statment including the full path

    use "L:\UserTyp\Frames\Usertypeframe.inc"


    is that right?

    ------------------

  5. #5
    Senior Member
    Join Date
    Jul 2001
    Location
    Westford, MA, USA
    Posts
    160
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Appstate (s)

    Basically, the compiler needs to read in the appstate definition before it calls the appstate. So you can define the appstate earlier in the .t file, or put it in an .inc file with a use statement at the top of the .t file, or add the .inc file to your use files in Options - Runtime -- it's all the same thing.

    An appstate, under the covers, is really just a function. And since there's no function prototyping with this compiler, you need to define the appstate before you can reference it.

    I'm not too keen on having you put the entire hard-coded path in your use statement. Can you put at least some of the common pathing in your use path (Options Runtime) so that you don't have to set up each machine's file structure in exactly the same way, and you'll be able to move files around more freely?

    AG

    ------------------

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 04:07 AM.

Copyright BetaSoft Inc.