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

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

Registration Username, Password And Enabling A Submit Button

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

    Registration Username, Password And Enabling A Submit Button

    On my registration page, I have a field for a Username, a field for Password, and a field for Confirm Password. I have a submit button at the bottom. I want the submit button to be disabled until the Username, Password, and Confirm Password has something typed in it from the user. What is the best way to do this? Is it by putting code into the enable expression on submit button? I tried this below in the enable expression on the submit button but it didnt work:

    USERNAME1.dialog.isDirty = true
    PASSWORD1.dialog.isDirty = true
    PASSWORD2.dialog.isDirty = true

    #2
    Re: Registration Username, Password And Enabling A Submit Button

    You should take a hard look at the alpha generated component for registration/signup as all of that is out of the box ready plus you can check out the other aspects that make it more user-friendly. It's not enough that the field is dirty...
    NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

    Comment


      #3
      Re: Registration Username, Password And Enabling A Submit Button

      It seems to be throwing an error on this below and wont complete the registration even if information is correct. Not sure how to modify it:


      function afterDialogValidate as v (e as p)


      'To edit this action, place insertion point anywhere in the command, then click the 'Action Scripting' button'.
      ExecuteServerSideAction("Save Web Security Values::SaveSecurity")



      dim e.javascript as c
      if rtc.flagWebSecurityhasGlobalError = .T. then
      e.javascript = e.javascript + "alert('"+rtc.WebSecurityGlobalErrorText+"');"
      else
      'no errors - new account was created

      'If this component is being run from the AppLauncher component, then after the user has added a new account
      'we want to hide this component and show the login screen. The following javascript will do this.
      'If this component is not being run from the AppLauncher, then the Javascript does nothing because the
      'MAINAPP_REGISTERNEWACCOUNT div will not exist.

      dim js_afterNewAccount as c
      js_afterNewAccount = <<%txt%
      //get a pointer to the DIV where the Register New Account component is shown. If this div exists
      var ele = $('MAINAPP_REGISTERNEWACCOUNT');
      if(ele) {
      ele.style.display = 'none';
      var ele2 = $('MAINAPPSPLASH');
      ele2.style.display = '';
      }
      %txt%

      e.javascript = e.javascript + ";" + crlf() + js_afterNewAccount


      end if




      'e.dataSubmitted - contains all values that were submitted by the Dialog
      'e.oldDataSubmitted - contains the original values in the controls

      '--------------------Repeating Sections ----------------------------------------
      'If your dialog contains repeating sections, data in the repeating sections will be in an array.
      'For example, say that your dialog has a repeating section that includes a field called QTY:
      'e.dataSubmitted.qty[1] - contains data from first repeating section row
      'e.dataSubmitted.qty[2] - contains data from second repeating section row, etc
      'e.dataSubmitted.favoriteColors[2][3] - contains data from the second row - 'favoriteColors' is a multi-select control - returns the 3rd choice the user made
      'e.dataSubmitted.qty.size() - number of entries in the array.

      'In addition, the e object will contain information about the repeating sections
      'e.repeatingSectionNames - a comma delimited list of the name (container ID) or each repeating section
      'e.repeatingSectionInfo - a property array with one entry for each repeating section.
      'The e.repeatingSectionInfo[] array will have these properties for each entry:
      ' - .activeRow - the row in the repeating section that had focus when the Dialog was submitted
      ' - .deletedRows - a CRLF delimited list of rows that were deleted. e.g. 1 and 3
      ' - .rowCount - a count of the number of non-deleted rows
      ' - .totalRowCount - a count of all rows in the repeating section including rows that were deleted
      ' - .fieldsInRepeating section - a CRLF delimited list of fields in the repeating section
      ' - .dirtyRowsInSection - a CRLF delimited list of rows in the repeating section that were edited. (A row that was edited, then deleted will still appear in this list).
      ' - .dirtyFieldsInSection - a CRLF delimited list of fields in the repeating section that were edited. for example: PARTNO_A5INSTANCE3 is the 'PARTNO' field in row 3.

      '-------------------------------------------------------------------------------------------


      'Also inside e:
      'e.tmpl = Component definition
      'e.rv = Request variables
      'session = Session variables
      'e.rtc = Runtime calculations - you can use this to store data to be passed to other server side events
      'e.arguments = SQL::Arguments object with values for each of the arguments defined in this component. To read a value from arguments: e.arguments.find("argumentName").data


      'You can can set these properties:
      'e.url - if you want to redirect to another page, set this property
      'e.javascript - if you want to send some javascript back to the browser, set this property.

      'You can set 'state' variables in this event. The value of any state variables will be available in all subsequent ajax callbacks.
      'To set a state variable:
      'e._set.myvar1 = "value1"
      'e._set.myvar2 = "value2"

      'To read the value of a 'state' variable that was previously set:
      'e._state.myvar1


      end function

      Comment


        #4
        Re: Registration Username, Password And Enabling A Submit Button

        What is the error?
        Last edited by CharlesParker; 07-07-2018, 09:58 AM.
        NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

        Comment


          #5
          Re: Registration Username, Password And Enabling A Submit Button

          I'm curious, are you using the app launcher?
          My registration component is an embedded object in a panel card so for the after new account, I have this:

          Code:
          dim js_afterNewAccount as c 
          	js_afterNewAccount = <<%txt%
          	
          		var po = {dialog.Object}.getParentObject();
          		po.panelSetActive('LOGIN',true);
          	}
          	%txt%
          	
          	e.javascript = e.javascript + ";" + crlf() + js_afterNewAccount
          So I can get back to the login panel card in the parent object after the registration is complete.
          NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

          Comment


            #6
            Re: Registration Username, Password And Enabling A Submit Button

            No my registration is just panel card. I just copied the guts from the registration template.

            Comment

            Working...
            X