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

Control Panel & Code Editor Helper: CP_Info()

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

  • MoGrace
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    @ Paul
    I got excited when I saw the video on Dock Panels using a MDI window and thought it would be great for displaying a Home form with a menu panel. But I never got very far on how to actually build one. So I am using a docked modeless dialog on a regular form that stays open as 'wallpaper', and can hide the toolbar menu whenever more space is needed. If a form is a MDI window, then you ought to be able to attach a dock panel to a form...?

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Latest version:

    cP_Info_20170926.txt

    Anybody know how to delete old attachments?

    Leave a comment:


  • pboomwork
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Your standard Alpha5 form or browse is a MDI window. Dialogs converted to MDI windows appear in all the A5 window list so they are not completely hidden. But they don't consume desktop space like a rolled up window. It's a personal preference thing 6 of one half dozen of the other. And sorry I missed/overlooked others instructions on adding this as a add in.

    Leave a comment:


  • Ray in Capetown
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Originally posted by MoGrace View Post
    Hi Paul,
    Can you explain the advantage of a MDI window to me vs a modeless Xdialog that stays open & can roll up so that it remains available AND visible? As I understand it, a MDI window becomes hidden when it is deactivated. But of course I may be wrong. BTW, I also included instructions on how to make this function appear in the right click menu on the Control Panel as an Addin.
    Where did you share the latest version

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    added an option to the subfunction to add restrictions when opening the default browse for a table
    Code:
    FUNCTION vw_defbrws as C (tname as C,vars as P)
    'DESCRIPTION: use to call a default browse with a set size and placement on 1st record    
        DIM brws as P
        WITH vars
            IF .not. is_object(brwsname) THEN
                brws = a5_open_default_Browse(tname)    
                'added a default restriction
                brws.restrict_enter = .t.
                brws.width = 800
                brws.height = 500        
                brws.window_position("left","top")
                'needed to clear the new record line 'ghost'
                brws.refresh_layout()
            ELSE
                brws = obj(brwsname)    
                brws.activate()        
            END IF        
                        
            brws.fetch_first()
    
            vw_defbrws = tname
    
        END WITH
    Thanks to Stan!
    Last edited by MoGrace; 09-25-2017, 01:36 PM. Reason: TO THANK STAN

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Hi Paul,
    Can you explain the advantage of a MDI window to me vs a modeless Xdialog that stays open & can roll up so that it remains available AND visible? As I understand it, a MDI window becomes hidden when it is deactivated. But of course I may be wrong. BTW, I also included instructions on how to make this function appear in the right click menu on the Control Panel as an Addin.

    Leave a comment:


  • pboomwork
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    I've used a rather old version of this function for years. it was one that someone, I don't know who at this point, turned into a Library and provided instructions on how to use as a addin.

    This newer version looked quite nice I don't know how many times I double clicked on a field of table name expecting it to appear in the code editor. The version I was using didn't do that, this one does.

    I've done some (actually a lot of work) on making Modeless Dialog boxes into MDI windows. MDI windows are what the standard form or browse use, they can be minimized and float behind other windows. I figured this function would be more usable as a MDI window, so I converted it to one.

    I've changed the name to CP_info2() to reflect the significant change in the way it works. At the first of the function are comments that explain how to make this Function into AEX library and use it as a AddIn accessed from the MenuBar in the Code editor just like the version I was previously using.

    The attachment also containts a Script DOC_Dialog_to_MDI this is the documentation I prepared some time ago on how to convert a existing Modeless Dialog into a MDI window, in case anyone is interested.

    cp_info2.txt
    Last edited by pboomwork; 01-20-2017, 03:23 PM.

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    I always thought that was just something arbitrary some people did in their scripts - hah! what do I know? not as much as I think...

    Leave a comment:


  • Ronald Anusiewicz
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Robin,

    'sets the default vertical spacing between controls.
    {ysize=.3}

    One ; is 1/3 a row spacing, two ;; is 2/3 a row spacing and three ;;; would be the same as {lf};

    Gives one a little more control on how the xDialog looks.

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Now we can add you to the credits! I don't see what the difference is in the section for Line 129 - is it the additional ' ; ' - what does that do?
    I do see that you made vField a multi select text box on line 159, I am curious to see how it works!

    Leave a comment:


  • Ronald Anusiewicz
    replied
    Re: Control Panel & Code Editor Helper: CP_Info()

    Hi Robin,

    I made some minor changes and tried to document what I did.
    The line numbers may be off slightly.
    While making my changes I did notice other credits:

    'Borrowed from ChrisHawkes & Peter.Greulich

    Chris and Peter, thank you!



    Code:
    line 64		
    '//Dlg Body Expanded
    dlg_body = <<%dlg%
    {removecomments}
    'use current font for line and character spacing
    {units=F}
    'sets the default vertical spacing between controls.
    {ysize=.3}
    
    changed [.25 to [.35 for longer file names
    Line 109	{font=Arial,10,n}{stretch=height}[.35,30vTable^#vTM!tc_*];
    
    changed line 129 from
    [.50,5idxdef^#idxdef];
    to [.50,5idxdef^#idxdef];;
    
    changed text=50
    Line 133  {text=42,3vTinfo1};
    
    changed line 159 from
    [.50,30vField^#vFM!fc_*];
    to [%M%.45,30vField^#vFM!fc_*];
    
    inserted after 156 
    <%T=Copy FIELD DEFINITIONS to lipboard;B=T;I=$$edit.clipboard.edit%!c_Fcopy>;
    
    
    added C_Fcopy after B_Fcopy
    
    ELSE IF a_dlg_button = "B_Fcopy" THEN
    	IF .not. fldflag THEN
    		END'
    	END IF
    	vField = format_data(vField,"C")
    	clipboard.Set_Data(EXTRACT_STRING(vField,"",","))
    ELSE IF a_dlg_button = "C_Fcopy" THEN
    	IF .not. fldflag THEN
    		END'
    	END IF
    	clipboard.Set_Data(vField)
    END IF
    
    %code%
    Attached Files

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel &amp; Code Editor Helper: CP_Info()

    Hi Ron,
    If you already know how to select multiple records in a list and copy to the clipboard - please share! And I will be happy to update the function. I guess that is why this was an ongoing project initially as others kept coming up with other things they wished the control panel did but doesn't. At least that is what got me thinking about it.
    Last edited by MoGrace; 01-15-2017, 04:39 PM. Reason: spelling - what else?

    Leave a comment:


  • Ronald Anusiewicz
    replied
    Re: Control Panel &amp; Code Editor Helper: CP_Info()

    Robin, again I'd like to thank you for sharing this tool. I use it every day.

    I do have a request. While I could make the change in my copy, I note that you are continuing development on your side.

    For me, it would be nice if the third column that contains the fields definitions where a multi select list and I could copy selected field definitions as a group to the clipboard. I do a lot of table manipulation using xbasic and I would find the ability to copy and paste a selected group of field definitions very handy.


    Thanks

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel &amp; Code Editor Helper: CP_Info()

    Added a line to the Table Info section to show when the selected file was last updated (had to fix an error if a set was clicked on)

    cP_Info_01-08-2017.txt

    Happy New Year
    Last edited by MoGrace; 01-08-2017, 02:20 PM.

    Leave a comment:


  • MoGrace
    replied
    Re: Control Panel &amp; Code Editor Helper: CP_Info()

    cP_Info-12-27-2016.txt

    Fixed a typo in the button event that opens/activates the code editor
    Last edited by MoGrace; 12-27-2016, 01:57 PM.

    Leave a comment:

Working...
X