|
midrange.com
Just to let you know, there is a menu item so that you do not need to
remember the 'extras' command. If you have not entered it, then you should
be able to select Actions->Enable Extras. This will bring up a dialog
where you can specify where you store your own macros (you can just leave
the entry field blank).
By default, when you invoke a macro the editor will look for that macro in
the c:\WDT400\MACROS directory. If you have enabled extras (by using the
menu item or using the 'extras' command), the editor will look in the
WDT400\EXTRAS directory and then the WDT400\MACROS directory. If when you
enabled extras you also specified your own directory, it will be searched
first and then WDT400\EXTRAS and then WDT400\MACROS. So, basically, the
'extras' command allows you to specify a path for the editor to search for
macros.
You can specify multiple directories when you enable extras. In the
dialog, just specify the all the directories using a semi-colon between
each (e.g. d:\mymacos;x:\yourmacros;z:\teammacros). You could use this to
specify a directory on a network drive in order to have a central
repository of macros which can be shared.
The WDT400\EXTRAS directory contains some additional macros which we
provide on an AS-IS basis. When you have enabled extras, you will see an
Extras menu in the editor which acccess some of these additional macros.
Integration with SoftLanding's TurnOver and Aldon's CMS is provided in this
way.
If you have your own macros, it is a good idea to specify your own
directory so that they are separate from the IBM supplied macros. This
just makes it easier when a new version of WDT is released and also avoids
the possibility of your updates being overwriten by new IBM macros.
When you open a file, a whole series of profiles are run (profiles are just
macros automatically run at certain times). You can modify some of them in
order to provide customizations (set key combinations, set menu items,
etc.).
profsys.lxu
xxx.lxl where xxx represents the source type of the file being opened
(e.g. for ILE RPG it is rpgle400.lxl)
xxx.lxu (if it exists - none come with the product) where xxx
represents the source type of the file being opened
profile.lx
You would normally modify the profile.lx to specify all the settings you
want to apply to all types of files. You would create/modify the
appropriate source type .lxu if you want to provide some setting that only
applies to files of that type. You should never touch the *.lxl files. To
see what .lxl and .lxu correspond to a source type, select
Options->Associations->Source type and then pick the source type in the
left column. The right column will then show the actual name for the .lxl
and .lxu file.
When the editor opens a file, it searches for these profiles using the same
mechanism as for regular macros so you can put your customizations in your
own directory.
Hope this helps,
Eric
Eric Simpson
IBM Canada Lab
Phone: (905) 413-3226, T/L: 969-3226, Fax: (905) 413-4850
Email: esimpson@ca.ibm.com
Internal mail: D1/140/8200/MKM
"Dave Schopp" <dschopp@imt.net>@midrange.com on 09/26/2001 12:28:34 PM
Please respond to code400-l@midrange.com
Sent by: code400-l-admin@midrange.com
To: <code400-l@midrange.com>
cc:
Subject: RE: Library lists confusion????????
I'm sure he did.
Here's what I typed:
"D:\WDT400>extras on d:\wdt400\mymacros"
Here's what CodeEdit said:
"The name specified is not recognized as an
internal or external command, operable program or batch file."
....Hmm...
I just hit the <Esc> key and tried it.
Now it seemed to work...
:-?
Well, dang. Guess I just needed to shut down all servers, reboot my
computer, start it up again, insert foot in mouth, and try it again? :-)
Thanks.
D
-----Original Message-----
From: code400-l-admin@midrange.com
[mailto:code400-l-admin@midrange.com]On Behalf Of Robin Coles
Sent: Wednesday, September 26, 2001 10:14
To: code400-l@midrange.com
Subject: RE: Library lists confusion????????
He might have meant "extras on D:\WDT400\MyMacros"
Cheers
Rob
-----Original Message-----
From: Dave Schopp [mailto:dschopp@imt.net]
Sent: 26 September 2001 16:57
To: code400-l@midrange.com
Subject: RE: Library lists confusion????????
Buck -
Where did you type in the "macros on " command?
I tried that from the CodeEdit window by pressing F9 but that didn't
work. So then I tried hitting Escape, then entering it, but that didn't
work either.
My macros are stored in the D:\WDT400\MyMacros\ folder. How do I let
CodeEdit know that?
D
-----Original Message-----
From: code400-l-admin@midrange.com
[mailto:code400-l-admin@midrange.com]On Behalf Of Buck Calabro
Sent: Tuesday, September 25, 2001 14:31
To: code400-l@midrange.com
Subject: RE: Library lists confusion????????
>profile.lx is automatically loaded whenever code/400 comes up so any
>command that you always want to execute can be put there.
Long ago, I made a copy of profile.lx and put it in another directory
where I keep all my Code macros. I then did a "macros on /buck/code"
(one time
only) to tell Code to use macros in that directory. It uses profile.lx
from there every time I start up now.
The help can be helpful if you have a bit of practise navigating.
Help, How do I... has stuff on customising and writing macros. Help,
Editor reference has stuff on settings you can detect and change.
--buck
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list To
post a message email: CODE400-L@midrange.com To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list To
post a message email: CODE400-L@midrange.com To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-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.
