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

xdialog Calendar

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

    xdialog Calendar

    Hi All,

    After changed the few codes from the "Calendar At A Glance" and other samples, I just made this xdialog Calendar. I could not figured the "Button object name" when I pressed a button from my xdialog. After I know the "object name" then I could write for Event code.

    Does any one know how to get the "object name" ?

    actdate = date()
    startdate = ctod(padl(alltrim(str(month(ActDate))),2,"0")+"/01/"+alltrim(str(year(ActDate))))
    startnum = dow(ctod(padl(alltrim(str(month(ActDate))),2,"0")+"/01/"+alltrim(str(year(ActDate)))))

    monthname=cmonth(Actdate)+" "+cyear(actdate)
    mnth=month(actdate)
    curr_month=cmonth(ActDate)
    curr_year=cyear(ActDate)

    btns =""
    daynum =""
    vShow =""


    dlg=<<%dlg%
    {can_exit=on_exit}
    {comment This first region contains the month name}
    {region}
    {font=Arial,14,B}
    {text=35,2:monthname}
    {font=Arial,8}
    {endregion};
    ;
    {comment Writing 'region=a' means that all identically designated regions
    will share the same horizontal tab dimensions.
    This second region contains the day of week header}
    {region=a}
    {font=Arial,12,B}
    S M T W T F S
    {endregion};
    {region=a}
    {font=Arial,12,b}
    %dlg%

    'create the button
    FOR i = 1 to 42 step 1
    vShow = alltrim(str(day(startdate-startnum+i)))
    dlg = dlg+"<%O={@@}%5,2 "+ vShow+"!x"+vShow+">" +If(i=7 .or. i=14 .or. i=21 .or. i=28 .or. i=35 .or. i=42,";"+crlf(),"")
    NEXT


    dlg = dlg+<<%dlg%
    {endregion};
    %dlg%

    code=<<%code%
    if a_dlg_button="on_exit" then 'when user presses the X in the upper right corner
    ui_modeless_dlg_close("@="+dlg_title)
    end if

    if left(a_dlg_button,1)="x" then
    a_dlg_button =""
    'how do I know the event or object name?
    msgbox("hello","what is this object name? "+left(a_dlg_button,2))
    end if

    %code%
    dlg_title="dlg_"+remspecial(time())
    eval(dlg_title)="Calendar At A Glance"
    ui_modeless_dlg_box("@="+dlg_title,dlg,code)

    #2
    Re: xdialog Calendar

    Code:
    ui_dlg_box("Test",<<%dlg% 
    
    Name: [.20name]; 
    <[COLOR="#FF0000"]OK[/COLOR]>; 
    %dlg%,<<%code% 
    debug(1)
    if a_dlg_button = "[COLOR="#FF0000"]OK[/COLOR]" then 
    'do something 
    end if 
    %code%)
    I think there's something wrong with your construction. If you run this the debugger window will open. Modify your code to include the debug(1) line as the first line of the code section and nothing happens.
    There can be only one.

    Comment


      #3
      Re: xdialog Calendar

      First, move the message box line to up above the a_dlg_button = "" since that sets the value of a_dlg_button to null and you can no longer see its value.

      Then, change the message box to:

      msgbox("hello","what is this object name? "+a_dlg_button)

      You will see that the value of a_dlg_button is X2 or x23 or x16 and you can use substr(a_dlg_button,2,2) to determine the date clicked.
      Finian

      Comment


        #4
        Re: xdialog Calendar

        thank you, Finian

        That works well.
        Last edited by johnkoh; 01-10-2014, 01:18 PM. Reason: error

        Comment


          #5
          Re: xdialog Calendar

          You're going to have a bit of a problem finding out whether the user chose the 29th of December or the 29th of January, etc.
          There can be only one.

          Comment


            #6
            Re: xdialog Calendar

            Stan,

            I think, I have the Month and year variables. KeyId = button object name+ month + year, then I will know the difference between 12/29 and Jan/29

            Comment


              #7
              Re: xdialog Calendar

              Hi,

              Update and I can get the date value now

              actdate = date()
              startdate = ctod(padl(alltrim(str(month(ActDate))),2,"0")+"/01/"+alltrim(str(year(ActDate))))
              startnum = dow(ctod(padl(alltrim(str(month(ActDate))),2,"0")+"/01/"+alltrim(str(year(ActDate)))))

              monthname=cmonth(Actdate)+" "+cyear(actdate)
              mnth=month(actdate)
              curr_month=cmonth(ActDate)
              curr_year=cyear(ActDate)

              btns =""
              daynum =""
              vShow =""
              dim List[42] as c


              dlg=<<%dlg%
              {can_exit=on_exit}
              {comment This first region contains the month name}
              {region}
              {font=Arial,14,B}
              {text=35,2:monthname}
              {font=Arial,8}
              {endregion};
              ;
              {comment Writing 'region=a' means that all identically designated regions
              will share the same horizontal tab dimensions.
              This second region contains the day of week header}
              {region=a}
              {font=Arial,12,B}
              S M T W T F S
              {endregion};
              {region=a}
              {font=Arial,12,b}
              %dlg%

              'create the button
              FOR i = 1 to 42 step 1
              vShow = alltrim(str(day(startdate-startnum+i)))
              list[i] = dtoc(startdate-startnum+i)
              dlg = dlg+"<%O={@@}%5,2 "+ vShow+"!x"+i+">" +If(i=7 .or. i=14 .or. i=21 .or. i=28 .or. i=35 .or. i=42,";"+crlf(),"")
              NEXT


              dlg = dlg+<<%dlg%
              {endregion};
              %dlg%

              code=<<%code%
              if a_dlg_button="on_exit" then 'when user presses the X in the upper right corner
              ui_modeless_dlg_close("@="+dlg_title)
              end if

              if left(a_dlg_button,1)="x" then
              'a_dlg_button =""
              'how do I know the event or object name?
              msgbox("hello","what is this object name? "+substr(a_dlg_button,2,2))
              'How to get the Value?
              msgbox("how to get the field value",list[val(substr(a_dlg_button,2,2))])
              end if

              %code%
              dlg_title="dlg_"+remspecial(time())
              eval(dlg_title)="Calendar At A Glance"
              ui_modeless_dlg_box("@="+dlg_title,dlg,code)

              Comment

              Working...
              X