[Ohrrpgce] SVN: james/9425 The Editor Slice Editor now has access to all special lookup codes. The

Ralph Versteegen teeemcee at gmail.com
Wed Sep 20 11:16:12 PDT 2017


Is there any advantage to hardcoding these lookup codes, and their
kindlimits, into the sliceeditor? I don't imagine we'll be editing existing
editor slice collections that often.
My idea had been to have a separate slicelookups.txt file in the data/
folder to be used for editor slice lookup codes, which would be negative.
(Replacing the normal slicelookups.txt, it would effectively hide the
game's lookup codes) But I'm not sure how easy that is to actually
implement.
It is useful to have constants like SL_EDITOR_SPLASH_MENU so that they can
be used in code. But they shouldn't be grouped with the other special
lookup codes, since they shouldn't appear in plotscr.hsd or the plotdict

On 21 September 2017 at 05:46, <subversion at hamsterrepublic.com> wrote:

> james
> 2017-09-20 10:46:16 -0700 (Wed, 20 Sep 2017)
> 284
> The Editor Slice Editor now has access to all special lookup codes. The
> are grouped right below any special codes that are preferred for the
> current filename, and above any user defined lookup codes (which are more
> or less meaningless in editor-specific slices... should I hide them?)
> ---
> U   wip/misc/sl_lookup.py
> U   wip/sliceedit.bas
> _______________________________________________
> Ohrrpgce mailing list
> ohrrpgce at lists.motherhamster.org
> http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.motherhamster.org/pipermail/ohrrpgce-motherhamster.org/attachments/20170921/35dc5f13/attachment-0001.html>


More information about the Ohrrpgce mailing list