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

Configure Editor Settings when editing an arbitrary value

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

  • Configure Editor Settings when editing an arbitrary value

    The editor configuration settings are generally set in the formview builder including:
    • Help text in editor
    • Field title in editor
    • User defined editor and template settings
    • Editor configuration genie


    However when launching an editor to edit an arbitrary value (not a form view field), how can the required settings be passed?

    The function to launch the editor for editing an arbitrary value is documented and includes a settings object but I can't find any documentation on how the additional editor configuration settings can be passed using the settings object.

    {dialog.object}.editorFromValue(UXEditorSet,valueToEdit,settingsObject);

    https://www.alphasoftware.com/docume...e%20Method.xml

    Does anyone know of a reference to the structure of the settings objects or how to define these settings for editing an arbitrary value?

  • #2
    Re: Configure Editor Settings when editing an arbitrary value

    I've solved my own mystery by picking up on some clues in the code from the standard editors plus a bit of debugging but I'll leave the post here as a reference for others that may stumble on this.

    A standard call to open an editor to edit an arbitrary value, passing the standard configuration options (Title and Help Text) as well as user defined values and Genie Settings (this example is the Genie Settings for the Numeric Keypad) is shown below. The standard configuration terms used are title, helpText and __genieSettings. User defined editor and template settings are just added at the top of the JSON settings object.

    Code:
    var valueToEdit = '';
    var settings = {
    	commit: function(value,settings) { 
    		console.log("Editor Returned value "+value);
    	},
    	title: "Test Title",
    	helpText: "Some Help Text",
    	aUserDefinedSetting: "Some custom value",
    	anotherUserSetting: {
    		sky: "Blue",
    		water: "Aqua" 
    	},
    	__genieSettings: {
    		size: 3,
    		align: 'left',
    		scale: true,
    		keypad: 'a',
    		customKeys: {
    			allow: false,
    			primary: {allow: true, value: ['*'], html: '*'},
    			secondary: {allow: true, value: ['/'], html: '/'}
    		},
    		negative: {
    			allow: false
    		},
    		decimal: {
    			allow: false,
    			char: '.',
    			places: -1
    		}
    	}
    }
    {dialog.object}.editorFromValue('EDITORSET_1','EDITOR_1',valueToEdit,settings);
    Note that the manner in which these values are processed is controlled by the code in the respective editor. In particular, the title is not currently displayed by default in the standard textbox editor because the code only sets the title if settings.formView is defined which is false when editing an arbitrary value though this was a quick fix to change that behavior to support both.

    Hope this helps someone.

    Comment


    • #3
      Re: Configure Editor Settings when editing an arbitrary value

      Nice sleuthing Jason. I was just about to post my findings on this... and saw you've figured it out. I'll post anyway... since I've gone through the process.

      The doc, both inline and online for .editorFromValue() are wrong... nasty error too. commit is a property of settings... so it's not commit = but rather commit: Makes you wonder if the code posted for documentation is ever actually tested.

      The Show Editor property of the Editor in use needs to be changed a bit. It starts with this statement...

      Code:
      if(typeof settings.formView != 'undefined')
      and since the editor is not being called from the formView none of its title and help text code will be run. So, comment out the opening if statement and it's ending... and the code will now run for both the .editorFromValue method and the formView control.

      Comment


      • #4
        Re: Configure Editor Settings when editing an arbitrary value

        Thanks David

        I didn't mention the errors in the documentation as I had already emailed the corrections to Alpha and whilst errors are not uncommon in Alpha documentation, I have never found a company more responsive to correcting any bugs and issues reported.

        The equals instead of colon was not the only error. The documentation is missing the second parameter (though the example code included the second parameter) however I would be surprised if these errors/omissions are not fixed very quickly. I have also suggested adding more documentation about the settings object in this function.

        I will also email Alpha with a suggestion to tweak the standard code in the editors to support both methods of launching. It's only a single line that needs to be inside that IF block, then the rest of the code executes as expected for either method of launching the editor.

        Code:
        var title = settings['title'];
        if(typeof settings.formView != 'undefined') { 	
        	if(typeof title == 'undefined' || title == '' ) title = settings.formView.active.name;
        }
        if(typeof title == 'undefined') title = '';

        Comment

        Working...
        X