Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook
Devcon 2020 Goes Virtual! LEARN MORE >

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

Embedded browse button bug & another similar bug...

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Embedded browse button bug & another similar bug...

    Another freakin' bug, and of course I find it...
    Why oh why is it always me that finds this stuff.......

    The embedded browse button event even is supposed to create "framework-code" as follows:
    (it doesn't and unless you paste it from v10.5, buttons in embedded browses are not setup to work properly.)

    The code below is what should be automatically added by a5.
    Note: Substitute red text for actual button name. (Substitute the column name in second bug). AN UNDERSCORE IS NEEDED

    Code:
    [COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]FUNCTION [/COLOR][/SIZE][COLOR=#ff0000][SIZE=1]ButtonName_[/SIZE][/COLOR][SIZE=1][COLOR=#000099]ButtonClick AS V ( event AS C, data AS C , row AS N )[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'DESCRIPTION: Fired when a button is clicked on a column.[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'Arguments:    event    - the name of the event that is fired[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'            data    - the data in the column cell[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'            row        - the row number in the browse[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'this.SetViewport_Row() sets the current row to the row with the button that was clicked.[/COLOR][/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=arial][COLOR=#000099]this.Set_Viewport_row(row)[/COLOR]
[/FONT][/COLOR][COLOR=#000080][FONT=arial]END FUNCTION[/FONT][/COLOR]
    Same problem exists if you try to use "Click fires user defined event" (on standalone browse) when selecting column title click behavior.
    (When you select "click fires user defined event.") Here again, framework code for the _TitleClick() should be created. It isn't.....

    Code:
    [FONT=arial][SIZE=1][COLOR=#000080]FUNCTION [/COLOR][COLOR=#ff0000]ColumName_[/COLOR][COLOR=#000080]TitleClick AS V (  )[/COLOR][/SIZE][/FONT]
[FONT=arial][SIZE=1][COLOR=#000080]'DESCRIPTION: If the browse click behavior is set to call a user defined event, this method is called when the title row of the browse is clicked.[/COLOR][/SIZE][/FONT]
[FONT=arial][SIZE=1][COLOR=#000080]END FUNCTION
[/COLOR][/SIZE][/FONT]' (I'm pretty sure that one of these functions is created for each column in the embedded browse, once you select this feature.)
    Never fails... Every time I move to a newer version, I take one step forward, and two steps back.
    (I find so many things like this it's almost comical.) All sorts of new features, but "core functionality" from previous versions is broken once again!
    Last edited by SNusa; 03-26-2012, 09:43 AM.
    Robert T. ~ "I enjoy manipulating data... just not my data."
    It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
    RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."
    Tags: None
    #2
    Re: Embedded browse button bug & another similar bug...

    Originally posted by SNusa View Post
    Another freakin' bug, and of course I find it...
    Why oh why is it always me that finds this stuff.......

    The embedded browse button event even is supposed to create "framework-code" as follows:
    (it doesn't and unless you paste it from v10.5, buttons in embedded browses are not setup to work properly.)

    The code below is what should be automatically added by a5.
    Note: Substitute red text for actual button name. (Substitute the column name in second bug).

    Code:
    [COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]FUNCTION [/COLOR][/SIZE][COLOR=#ff0000][SIZE=1]ButtonName_[/SIZE][/COLOR][SIZE=1][COLOR=#000099]ButtonClick AS V ( event AS C, data AS C , row AS N )[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'DESCRIPTION: Fired when a button is clicked on a column.[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'Arguments:    event    - the name of the event that is fired[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'            data    - the data in the column cell[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'            row        - the row number in the browse[/COLOR][/SIZE]
[/FONT][/COLOR][COLOR=#000000][FONT=arial][SIZE=1][COLOR=#000099]'this.SetViewport_Row() sets the current row to the row with the button that was clicked.[/COLOR][/SIZE][/FONT][/COLOR]
[COLOR=#000000][FONT=arial][COLOR=#000099]this.Set_Viewport_row(row)[/COLOR]
[/FONT][/COLOR][COLOR=#000080][FONT=arial]END FUNCTION[/FONT][/COLOR]
    Same problem exists if you try to use "Click fires user defined event" (on standalone browse) when selecting column title click behavior.
    (When you select "click fires user defined event.") Here again, framework code for the _TitleClick() should be created. It isn't.....

    Code:
    [FONT=arial][SIZE=1][COLOR=#000080]FUNCTION [/COLOR][COLOR=#ff0000]ColumName_[/COLOR][COLOR=#000080]TitleClick AS V (  )[/COLOR][/SIZE][/FONT]
[FONT=arial][SIZE=1][COLOR=#000080]'DESCRIPTION: If the browse click behavior is set to call a user defined event, this method is called when the title row of the browse is clicked.[/COLOR][/SIZE][/FONT]
[FONT=arial][SIZE=1][COLOR=#000080]END FUNCTION
[/COLOR][/SIZE][/FONT]' (I'm pretty sure that one of these functions is created for each column in the embedded browse, once you select this feature.)
    Never fails... Every time I move to a newer version, I take one step forward, and two steps back.
    (I find so many things like this it's almost comical.) All sorts of new features, but "core functionality" from previous versions is broken once again!
    That's where I'm at...

    What version works? v1?

    Does anybody have v1?

    It IS ok to call me 513-484-0143

    Comment

      #3
      Re: Embedded browse button bug & another similar bug...

      All you have to do is edit the Browse event event, and add the code in blue. (And replace the red ButtonName_ with your button's name)
      The underscore must be included too. (IE: if button name is SUBMIT, use SUBMIT_ButtonClick.
      Any extra code you add to the "event event" is placed: after this.Set_Viewport_row(row) and before END FUNCTION

      Just copy and use the code sections from my OP above, and use it. (It' why I added it there.)

      I've attached a highly modified AlphaSports Invoice you can import into AlphaSports. (right click on the browse buttons to see different working examples) One "really cool" button is the quantity button. ~ It looks like a field, but acts like a button. (which in turn updates data outside the browse on click)

      This modified v10.5 Alpha Sports Invoice layout is one of the layouts I used to learn "stuff." Invoice.a5pkg
      ~I have several other layouts with other "core-code" examples too.

      Note: I built this in v.10.5 and am working with it in v.11. I'm using the entire 10.5 version of Alphasports (generated from v.10.5) in v.11, not just this one layout. But I believe it will work fine if you just import this one layout into v.11.

      tip: Create a new Alpha Sports sample database before importing. (To avoid problems, you probably will also want to delete the original Invoice layout in this new database first.)
      Last edited by SNusa; 03-26-2012, 09:41 AM.
      Robert T. ~ "I enjoy manipulating data... just not my data."
      It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
      RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

      Comment

        #4
        Re: Embedded browse button bug & another similar bug...

        This bug has been confirmed and will be addressed in next v.11 update....
        Robert T. ~ "I enjoy manipulating data... just not my data."
        It's all about the "framework." (I suppose an "a5-induced" hard drive crash is now in order?)
        RELOADED: My current posting activity here merely represents a "Momentary Lapse Of Reason."

        Comment

        Previous template Next
        Working...
        X