|
You should look at the section of the manual dealing with this -- they make recommendations about where user defined macros should be stored, and it tells you more about the different profiles which can be used. http://localhost:49213/cgi-bin/vahwebx.exe/vahelp/va400/Extract/0/lpex/tasks/tlperpro.htm#top fkany@xxxxxxxxxxxxxxxxxx Sent by: code400-l-bounces@xxxxxxxxxxxx 02/20/2003 09:58 AM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> To CN=CODE/O=400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc Subject Re: macro buttons for the tool bar Sweeeet!!! It's working just fine. I can now see how I can add more buttons do more complex functions other than "Alt + L". Thanks, Frank Jeff@xxxxxxxxxx@midrange.com on 02/20/2003 07:17:34 AM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> Sent by: code400-l-bounces@xxxxxxxxxxxx To: CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc: Subject: Re: macro buttons for the tool bar The SET TOOLBAR command should go into PROFILE.LX. That file is loaded every time you start Code. fkany@xxxxxxxxxxxxxxxxxx Sent by: code400-l-bounces@xxxxxxxxxxxx 02/19/2003 05:13 PM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> To CN=CODE/O=400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc Subject Re: macro buttons for the tool bar Jeff, I haven't been successful in creating a toolbar button for "ALT + L". Do you see anything missing in the markline.lx or markline.lxl files? When I created these files in the "C:\WDT400\macros" directory I closed out of CODE400 and then restarted the application but nothing appears to be changed in the toolbar. MARKLINE.LX file =========================== C:\WDT400\macros\markline.lx =========================== /* keystroke record and playback macro. Save to macros directory */ /* execute using 'macro macroFilename.' */ "check" "lxi LP_MARKLINE" MARKLINE.LXL file =========================== C:\WDT400\macros\markline.lxl =========================== /* markline.LXL - Marks a line of code in edit mode */ 'SET TOOLBAR.markline BITMAP _35 HELP "Mark Line" 35 MACRO markline' Jeff@xxxxxxxxxx@midrange.com on 02/19/2003 10:24:09 AM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> Sent by: code400-l-bounces@xxxxxxxxxxxx To: CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc: Subject: Re: macro buttons for the tool bar To create a toolbar button, you use the syntax: set toolbar.Name[BITMAP resddl_id] [ HELP HelpText] [OrdinalNumber] [ Command] Options Name Name for the item to be included on the new tool-bar menu. This name is also used as the text label on the new tool-bar menu item. To include a blank in the name, use the underscore character (_). BITMAP Specifies that the new tool-bar item is a bitmap. If used, you must also specify: resdll The resource dll containing the new item's bitmap. id The id for the bitmap contained in the resdll resource dll. HELP Optional hover-help text specified by HelpText, enclosed in quotes. When you pause the mouse cursor over your tool-bar item, this text will appear in a bubble near the mouse cursor. OrdinalNumber The position at which the tool-bar item is inserted, starting at zero. If the number is greater than the first available position, or if no number is specified, the first available position is used. Command The action or actions to perform when the tool-bar item is selected. Description The toolbar parameter sets the tool-bar menu by adding or removing user-defined items from the tool-bar. It can also remove default Editor window tool-bar items. If only the name of an existing tool-bar item is given when setting the toolbar parameter, that item is deleted from the tool-bar menu. When specifying the name of user-defined tool-bar items, Name is case-sensitive. You must enter the tool-bar item text name exactly as it appears. Where a space appears, substitute the underscore character ( _ ). So, in my example, 'set toolbar.BUTTONNAME BITMAP_33 HELP "Tooltip text" 4 MACRO MACRONAME' Replace BUTTONAME with the some unique name. BITMAP_33 is the icon that will be used. The icon must be in a DLL in your PATH. Replace "Tooltip text" with the description of your macro. 4 is the position of the new icon. In this case, the new icon will appear after the 4th icon. Replace MACRONAME with the name of the macro you want to run. fkany@xxxxxxxxxxxxxxxxxx Sent by: code400-l-bounces@xxxxxxxxxxxx 02/19/2003 10:51 AM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> To CN=CODE/O=400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc Subject Re: macro buttons for the tool bar Jeff, I recorded "ALT + L" for marking a line, here's out it's saved in : C: \WDT400\macros\Markline.lx /*---------------------------------------------------------------*/ /* keystroke record and playback macro. Save to macros directory */ /* execute using 'macro macroFilename.' */ /*---------------------------------------------------------------*/ "check" "lxi LP_MARKLINE" Would you show me how to make a button on the toolbar? I'll then take that example to create "ALT + C", "ALT + M", "ALT + U", etc... buttons. Thanks, Frank Jeff@xxxxxxxxxx@midrange.com on 02/18/2003 04:07:52 PM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> Sent by: code400-l-bounces@xxxxxxxxxxxx To: CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> cc: Subject: Re: macro buttons for the tool bar For example: 'set actionbar.~Macros.RPG~COMMENT MACRO RPGCOMMENT' 'set toolbar.OPENRPG BITMAP_33 HELP "Open RPG source" 4 MACRO RPGOPEN' 'set toolbar.OPENDDS BITMAP_33 HELP "Open DDS source" 5 MACRO DDSOPEN' 'set toolbar.CreatePROC BITMAP_31 HELP "Create Procedure" 6 macro runjava LpexRPGProcSG' 'set toolbar.CreateDSPEC BITMAP_32 HELP "Create D-spec" 7 macro runjava LpexDSpecSG' 'set toolbar.COMPHEAD BITMAP _34 HELP "Insert RPGLE Compile Heading" 8 MACRO RPGLECOMPILE' /* Alt keys */ 'set action.a-t focus.row 3' /* Ctrl keys */ 'set action.c-c MACRO CLIPLINE COPY' 'set action.c-f MACRO ISD_FIND' 'set action.c-v MACRO CLIPLINE PASTE' 'set action.c-x MACRO CLIPLINE CUT' /* Other keys */ 'set action.del MACRO ISD_DELETE1' "John Larimer" <jklarimer@xxxxxxxxxxx> Sent by: code400-l-bounces@xxxxxxxxxxxx 02/18/2003 04:34 PM Please respond to CODE/400 Discussion & Support <code400-l@xxxxxxxxxxxx> To "CODE/400 Discussion & Support" <code400-l@xxxxxxxxxxxx> cc Subject Re: macro buttons for the tool bar Frank: You will want to use the 'SET' command and the 'TOOLBAR' parameter. Under 'Help' 'Editor Reference', you will find documentation for both commands and parameters. Other useful items you can 'SET' are: ACTION = Keyboard Key ACTIONBAR = Add items to the Menu Bar POPUPMENU = Right Mouse Click Good luck, John ----- Original Message ----- From: <fkany@xxxxxxxxxxxxxxxxxx> To: <code400-l@xxxxxxxxxxxx> Sent: Tuesday, February 18, 2003 1:09 PM Subject: macro buttons for the tool bar > I've just started using CODE/400 for editing RPG programs on a V5R2 box. > Is there a way to add a macro button to the tool bar? I would like to > record a macro for marking, unmarking, copying, and moving lines. Having > to press ALT + L, ALT + C, etc... everytime I want to copy a line seems to > slow me down when coding. > > TIA, > > Frank > > _______________________________________________ > This is the CODE/400 Discussion & Support (CODE400-L) mailing list > To post a message email: CODE400-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/code400-l > or email: CODE400-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/code400-l. > > NOTE: WDSc for iSeries disucssion has it's own mailing list. > Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l > > _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/code400-l or email: CODE400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
