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

Watched Controls

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

  • Watched Controls

    Done this in a Grid, but where do I set the "watched" function in a UX control in the detail view?
    Regards

  • #2
    Re: Watched Controls

    To add to this question, I have a Function library with functions. I would like to call this function to calculate the value of a control(detailview) by the change if fields(watched) on the detailview.
    Ideal is to set these values just before the record is written away. At which event will this be done. The fields I want to update are hidden on the detailview.
    Regards

    Comment


    • #3
      Re: Watched Controls

      The UX Watch Events has not been implemented like the Grid Watch Events. Information on Watch Events is very tough to find. The dialog.Object property you're looking for is .dialogWatches. .dialogWatch doesn't exist in the documentation. I'm shaking my head right now. Alpha is really bad at this stuff.

      You'll only find a reference to .dialogWatches in the release notes... http://aadocuments.s3.amazonaws.com/...easeNotes.Html. Search for dialogWatches. The example is poorly implemented and badly explained.

      I'm not sure dialogWatches will help you with a List Detail View. Implemented as suggested in the notes... in the Client-side Event beforePrepare, what you get is the watch firing every time you select a row in the List and the Detail View gets populated. This is probably not what you want. Here is the code posted in the notes...

      Code:
      {dialog.Object}.dialogWatches['MY_WATCH_EVENT'] = {
          watch: ['TEXTBOX2'],
          variables: [],
          updateColumn: 'TEXTBOX1',
          onChange: function(data) {
              var dialog = {};
              var summary = {};
              {dialog.Object}._getDialogVariables(dialog,summary,data);
              var txt2 = {dialog.object}.getValue('textbox2');
              {dialog.Object}.setValue('TEXTBOX1', {dialog.object}._functions.myFunc2(txt2) );
          }
      }
      In your Javascript Function section, add this...

      Code:
      {dialog.Object}._functions.myFunc2 = function(inData){
      
      	return inData + "4444";
      
      }
      Finally, for some reason, Alpha left in a console message... so that for every row in the List, when the target field gets updated, a console message is pushed out. I'm shaking my head again.

      Anyway... maybe some of this will get you started.

      Comment


      • #4
        Re: Watched Controls

        Many thanks,

        Just got back from a trip so took long to acknowledge your help.
        Will check it out.
        Regards

        Comment


        • #5
          Re: Watched Controls

          It would seem to me that you can set this up a different way. Have an action triggered based on when the user wants to exit the form, or when the form is "dirty", and each time it calculates what you want. You could create an array of form fields to collect intial state and end state, find variances, then apply some formula to do what you want. Further, you could store the panel, fields, and expressions in a database so that it could all be done dynamcally.

          Anyway, I think there are more ways to do what you want, although what David mentions will probably work fine and be the easist to impliment.

          Comment

          Working...
          X