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

UX isDirty Discussion

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

    UX isDirty Discussion

    This is a really interesting subject because there are a more than a few posts over the years... and just recently, regarding the isDirty state of a UX... and how to set it Clean manually. In the normal course of events you shouldn't need to do this... but we all know "normal" is not always the case.

    The information here deals with both the Data Bound and Unbound UX. I'm not positive I've got all of it... but... it's a discussion.

    There's a whole lot going on when a UX goes dirty... or clean.

    This method does some of the job...

    Code:
    {dialog.Object}._setRowState(1,false);
    I believe this does the same as the following four statements...

    Code:
    {dialog.Object}._isDataDirty = false;
    {dialog.Object}._isDirty = false;
    {dialog.Object}._dirtyRows[0] = false;
    {dialog.Object}.refreshClientSideComputations();
    But... doing only this part leaves the UX in an odd state... because the data control that is dirty, is still marked as dirty.

    Rich mentioned ._setRowState and Frank mentioned .setAttribute for a5IsDirty... but these 2 need to be used together in order to return the UX to a clean state. NOTE... not the data... but rather the state of the UX.

    Using ._setRowState by itself results in an odd looking behaviour: Make a control dirty, use ._setRowState, and then alter that same control again. The UX does not go dirty... because the a5IsDirty attribute for that control is already "true" and therefore it does not trigger the "dirty" process for the UX. The odd looking behaviour is that if you focus on another control after making your first control dirty again, then the UX does go dirty.

    So... we need to alter all the "dirty" properties of the UX... and... alter all the "a5IsDirty" attributes of any dirty controls.

    We know how to change the "dirty" properties... now how do we alter a5IsDirty?

    If using a Data Bound UX we have the property {dialog.Object}._dataBoundControls. This is an Array of all the Data Bound Controls. We can loop through this array do the work.
    For an Unbound UX we need to do something else. We can use the Object property {dialog.Object}.columnInfo. This is an Object of column Objects. We can loop through this Object grabbing the keys... which are the Column Names. We can push those names into an Array and then work on a5IsDirty.
    A Data Bound UX also has {dialog.Object}.columnInfo so, actually, we can just use that for Data Bound or Unbound.

    Looping through the Array of Column Names, we use $ga to get access to a5IsDirty. If it's "true" then we push that element into an Array of dirty elements.

    Once we have our Array of dirty elements, we can use $sa to reset all the a5IsDirty attributes to false.

    Doing this, the odd looking behaviour is now gone. You can alter the originally changed control... and the UX will go dirty again right away.

    Here is the code for doing all this...

    Code:
    //take care of the UX dirty properties... setting them back to clean.
    {dialog.Object}._setRowState(1,false);
    
    //use the Data Bound UX _dataBoundControls to get an array of columns
    var columnNames = {dialog.Object}._dataBoundControls;
    
    //using a Data Bound or Unbound UX, you can also use the dialog object columnInfo
    //var columnNames = [];
    //for(var k in {dialog.Object}.columnInfo) columnNames.push(k);
    
    //now, loop through the columns and use $ga to get the a5IsDirty attriubte value
    //if a5IsDirty is "true" then add it to an array of dirty elements
    var dirtyEle = [];
    var isEleDirty;
    for(var i=0; i<columnNames.length; i++){
    	isEleDirty = $ga('{dialog.ComponentName}.V.R1.'+ columnNames[i],'a5IsDirty');
    	if(isEleDirty[0] == "true"){
    		dirtyEle.push('{dialog.ComponentName}.V.R1.'+ columnNames[i])
    	}
    }
    
    //if we have an array of dirty columns, use $sa to set the attriubte a5IsDirty to false for all the columns
    //$sa takes an Array of elements to work on.
    if(dirtyEle.length > 0){
    	$sa(dirtyEle,'a5IsDirty',"false");
    }
    The end result is a Clean UX... with... changed data. We've now separated the two... as the UX no longer automatically knows that any data has been changed.

    This is not something that Alpha would intend to do... but... Alpha let's us do some very cool things.

    #2
    Re: UX isDirty Discussion

    Alpha let's us do some very cool things.
    Very cool...
    Win 10 64 Development, Win 7 64 WAS 11-1, 2, Win 10 64 AA-1,2, MySql, dbForge Studio The Best MySQL GUI Tool IMHO. http://www.devart.com/dbforge/mysql/studio/

    Comment

    Working...
    X