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

How to prevent insertion point from disappearing in code editor?

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

    How to prevent insertion point from disappearing in code editor?

    Okay, this is really driving me crazy now. Not all the time, but enough to be annoying, the insertion point in the code editor continually disappears on me. It all starts when I am in some other application and then switch back to Alpha and continue typing in the code editor. As soon as I start typing the insertion point will vanish and it won't come back until I switch back-and-forth to another application. But the insertion point again vanishes when I start typing. I have to save my code, close the component and then re-open it. Does this happen to other people?

    #2
    Re: How to prevent insertion point from disappearing in code editor?

    Originally posted by RichCPT View Post
    Okay, this is really driving me crazy now. Not all the time, but enough to be annoying, the insertion point in the code editor continually disappears on me. It all starts when I am in some other application and then switch back to Alpha and continue typing in the code editor. As soon as I start typing the insertion point will vanish and it won't come back until I switch back-and-forth to another application. But the insertion point again vanishes when I start typing. I have to save my code, close the component and then re-open it. Does this happen to other people?
    I don't have a solution, but I run into this issue all the time. Maybe we should collaborate to create a reliable reproduction of the issue and send it to Alpha. It makes writing code incredibly difficult once you lose the cursor. :/
    Alpha Anywhere latest pre-release

    Comment


      #3
      Re: How to prevent insertion point from disappearing in code editor?

      Does this happen to other people?
      yes it is annoying, you don't even have to switch to something, just preview the component or the pages. then come back because you need to do some adjustment, the cursor will go somewhere visiting a friend.
      it is a guessing game from then on. there is no way to predict this.
      Maybe we should collaborate to create a reliable reproduction of the issue
      i could post a screencast if you like.
      there is nothing special that alpha needs to replicate it. it just happens.
      thanks for reading

      gandhi

      version 11 3381 - 4096
      mysql backend
      http://www.alphawebprogramming.blogspot.com
      [email protected]
      Skype:[email protected]
      1 914 924 5171

      Comment


        #4
        Re: How to prevent insertion point from disappearing in code editor?

        I used to get this all of the time until I installed Windows 10 (was running Win 7 before). Under Windows 10 I don't get this anymore.
        Mike Brown - Contact Me
        Programmatic Technologies, LLC
        Programmatic-Technologies.com
        Independent Developer & Consultant​​

        Comment


          #5
          Re: How to prevent insertion point from disappearing in code editor?

          Oh good, it's not just my computer.

          Maybe Alpha could weigh-in on this issue?

          Comment


            #6
            Re: How to prevent insertion point from disappearing in code editor?

            Originally posted by mikeallenbrown View Post
            I used to get this all of the time until I installed Windows 10 (was running Win 7 before). Under Windows 10 I don't get this anymore.
            Same here
            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


              #7
              Re: How to prevent insertion point from disappearing in code editor?

              It's BUG! It wasn't always there, but at some point in v11 it showed up. In my case, it's in xbasic grid events where the problem ALWAYS crops up! GGGRRRRR!!!!
              Peter
              AlphaBase Solutions, LLC

              [email protected]
              https://www.alphabasesolutions.com


              Comment


                #8
                Re: How to prevent insertion point from disappearing in code editor?

                Right, I seem to recall it starting some point after improvements were made to auto-complete in the code editor. I don't recall if I'd switch to V12 by that time or not.

                Comment


                  #9
                  Re: How to prevent insertion point from disappearing in code editor?

                  All, thanks for responding. (I'm collecting some more info on the issue for Alpha.)

                  Do any of you recollect if the I-beam cursor is more apt to vanish when a particular windows app is opened, or when our alpha web app is open in a browser while coding, or when a particular web site is viewed while coding? And, if it is related to having the browser open does Chrome, IE or Firefox make any difference?

                  Peter, you said the problem, "ALWAYS", happens in a Grid under the XBasic events. Do you have a sequence we could follow to reproduce it and does it fail 100% of the time?

                  Alpha indicated to me that the editors in the UX might already have some code to handle issues about the vanishing cursor on the gain focus event.

                  Does anyone recall if the cursor vanishes in a UX?

                  The other important information to collect, is the AA version/build number: I mostly use AA 12.3/2689.

                  Comment


                    #10
                    Re: How to prevent insertion point from disappearing in code editor?

                    Peter, you said the problem, "ALWAYS", happens in a Grid under the XBasic events. Do you have a sequence we could follow to reproduce it and does it fail 100% of the time?
                    Not that I'm aware of. I just start coding in an event and within a minute or so, Poof!, it's gone.
                    Peter
                    AlphaBase Solutions, LLC

                    [email protected]
                    https://www.alphabasesolutions.com


                    Comment


                      #11
                      Re: How to prevent insertion point from disappearing in code editor?

                      Alpha said we should let them know about this issue if it happens in the most recent pre-release, so that would be like version 12.3 build 3389 or higher! At the moment I don't spend much time in pre-release versions, so, if someone else finds this maybe tell them about it.

                      Comment


                        #12
                        Re: How to prevent insertion point from disappearing in code editor?

                        this is from version 11 i do not know if it the same over there in the colorful world of alpha anywhere.
                        if you are editing and preview the result, in a grid just now, and return to the editor the insertion point goes away. i can repeat it as many times i want. the save the component the insertion point comes back.
                        will post a video in a minute.

                        http://screencast.com/t/icc1c2qCo
                        Last edited by GGandhi; 01-30-2016, 09:38 PM.
                        thanks for reading

                        gandhi

                        version 11 3381 - 4096
                        mysql backend
                        http://www.alphawebprogramming.blogspot.com
                        [email protected]
                        Skype:[email protected]
                        1 914 924 5171

                        Comment


                          #13
                          Re: How to prevent insertion point from disappearing in code editor?

                          Gandhi,
                          Thanks for the video. I have confirmed the steps you demonstrated always vanishes the cursor in at least Ver 11 Build 3678 and Ver 12.3 Build 2689.

                          The cursor does NOT vanish using those steps in Ver 12.3 Build 2999 or Ver 12.3 Build 3360.

                          Comment


                            #14
                            Re: How to prevent insertion point from disappearing in code editor?

                            Is there a patch available for this? This a really annoying bug!

                            It may be fixed in a newer build (I am on 2689), but I am unable to do a full upgrade to that build.
                            Maybe it is related to the problem where the code completion popup hides the line I am typing on!!!

                            Comment


                              #15
                              Re: How to prevent insertion point from disappearing in code editor?

                              Yes, it was fixed in a later update - around build 3389.

                              Comment

                              Working...
                              X