Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Scripteditor_Open() Interactive Window issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Scripteditor_Open() Interactive Window issue

    This is an odd bug of the script editor (fails in A5v8 through A5v11, probably earlier versions too) that is illustrated with a simple example. This is a case where code<>code.

    I believe it has something to do with the environment of the interactive window (WITH-END WITH) but can't get the test function to ever work when run from the interactive window. The only real difference is executing Scripteditor_Open()
    function individually vs running the same code in a function from the Interactive Window. When run from other Alpha locations, it seems to work.

    The 1st Scripteditor_Open() always works in the function, but subsequent ones fails.

    Here is a test function with notes in it:
    Code:
    FUNCTION test_code_ed AS C (funcname1 AS C, funcname2 AS C, funcname3 AS C )
    'DESCRIPTION: Test code Editor scripteditor_open() function
    
    ' Illustrates unexplained error.  Fails in A5v8 through A5v11, perhaps earlier as well.
    ' function names can be either "functionname1" or "functionname1()", use names of your own functions
    
    ' Running 3 scripteditor_open() lines from the interactive editor (select all text, use lightning bolt)
    ' or run each individually produces no error, as in
    '        scripteditor_open("functionname1","function")
    '        scripteditor_open("functionname2","function")
    '        scripteditor_open("functionname3","function")
    
    ' However, when this function is run from the Interactive Window, as in
    '        test_code_ed("functionname1", "functionname2", "functionname3")
    ' it will fail at the opening of the 2nd and 3rd scripts
    '        
    Statusbar.Set_Text("Opening Function: "+funcname1)
    scripteditor_open(funcname1,"function")
    Statusbar.Set_Text("Opening Function: "+funcname2)
    scripteditor_open(funcname2,"function")
    Statusbar.Set_Text("Opening Function: "+funcname3)
    scripteditor_open(funcname3,"function")
    
    END FUNCTION
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture



  • #2
    Re: Scripteditor_Open() Interactive Window issue

    Just to be complete, in a similar way, UDF_Design() (and I suspect Script_Design() as well) does exactly the same thing. Here is it's test code:
    Code:
    FUNCTION test_code_ed AS C (funcname1 AS C, funcname2 AS C, funcname3 AS C )
    'DESCRIPTION: Test code Editor scripteditor_open()/UDF_Design() function
    
    ' Illustrates unexplained error.  Fails in A5v8 through A5v11, perhaps earlier as well.
    ' function names can be either "functionname1" or "functionname1()", use names of your own functions
    
    ' Running 3 scripteditor_open() or UDF_Design lines from the interactive editor (select all text, use lightning bolt)
    ' or run each individually produces no error, as in
    '		scripteditor_open("functionname1","function")
    '		scripteditor_open("functionname2","function")
    '		scripteditor_open("functionname3","function")
    
    ' However, when this function is run from the Interactive Window, as in
    '		test_code_ed("functionname1", "functionname2", "functionname3")
    ' it will fail at the opening of the 2nd and 3rd scripts
    '		
    Statusbar.Set_Text("Opening Function: "+funcname1)
    'scripteditor_open(funcname1,"function")
    udf_design(funcname1,"")
    
    Statusbar.Set_Text("Opening Function: "+funcname2)
    'scripteditor_open(funcname2,"function")
    udf_design(funcname2,"")
    
    Statusbar.Set_Text("Opening Function: "+funcname3)
    'scripteditor_open(funcname3,"function")
    udf_design(funcname3,"")
    
    END FUNCTION
    Addendum: The test_code_ed("functionname1", "functionname2", "functionname3") line fails if you press enter at the end of the line in the Interactive editor, but not if you select the code, then press the lightning bolt.
    Last edited by csda1; 10-26-2011, 05:30 PM. Reason: Additional info
    Regards,

    Ira J. Perlow
    Computer Systems Design


    CSDA A5 Products
    New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
    CSDA Barcode Functions

    CSDA Code Utility
    CSDA Screen Capture


    Comment


    • #3
      Re: Scripteditor_Open() Interactive Window issue

      Hi Ira. I observe the same behavior in A5v9 as you are reporting. I presume you are using A5 code editor functions in CSDA. I use them in my PGPre utility and I have to admit to a lot of arm wrestling with these functions to get them to work correctly.

      Anyway, this may help. I notice if I run your 'test_code_ed()' from the interactive tab of the code editor window, I get the errors you describe. However I also notice that if I create a global script (instead of a UDF) that contains just a single line of code 'test_code_ed()' without the quotes, save it and then run that script from the code tab of the control panel (not the interactive tab), then it works OK.

      If I try and run this script from the interactive code window using script_play(), I still get the same error.

      Now I am not sure this suggests a work-around to you, but I certainly hope so. These are clearly some bugs in these A5 functions that could do with some investigation by someone who has access to their code.

      Comment


      • #4
        Re: Scripteditor_Open() Interactive Window issue

        Hi Brett,

        Originally posted by brett s View Post
        Hi Ira. I observe the same behavior in A5v9 as you are reporting. I presume you are using A5 code editor functions in CSDA. I use them in my PGPre utility and I have to admit to a lot of arm wrestling with these functions to get them to work correctly.
        Actually, I don't have any problems, except if a function or a script_play is run from the interactive window followed by a return. If you select (highlight the code) in the interactive window, then press the lightning bolt, it works.

        This implies that the lightning bolt execution is not really the same as hitting enter at the end of a single line.

        Originally posted by brett s View Post
        Anyway, this may help. I notice if I run your 'test_code_ed()' from the interactive tab of the code editor window, I get the errors you describe. However I also notice that if I create a global script (instead of a UDF) that contains just a single line of code 'test_code_ed()' without the quotes, save it and then run that script from the code tab of the control panel (not the interactive tab), then it works OK.

        If I try and run this script from the interactive code window using script_play(), I still get the same error.

        Now I am not sure this suggests a work-around to you, but I certainly hope so. These are clearly some bugs in these A5 functions that could do with some investigation by someone who has access to their code.
        This does not give a workaround, and effectively, you are doing exactly the same thing, whether a script or function. The point is primarily to allow someone to invoke a process (the CSDA code Utility) from the Interactive Window. I haven't found any workaround that can be in the code itself.

        Another piece that may point to something is that if I open another XDialog box that has a code editor/Interactive Window, it works from that Interactive window. So it is specific to the Code Editor's Interactive Window.

        I have tried a variety of With-End With statements in order to provide the code pointer's environment, but has not worked to date.

        Thanks for your input though. Maybe Alpha will comment.

        The real point is that somehow the environment at execution of single line is not allowing the code editor's window and it's properties to be available (despite the context showing the code editor).
        Regards,

        Ira J. Perlow
        Computer Systems Design


        CSDA A5 Products
        New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
        CSDA Barcode Functions

        CSDA Code Utility
        CSDA Screen Capture


        Comment

        Working...
        X