first commit - moved from local dev to git

This commit is contained in:
firebee
2022-10-02 10:09:40 +02:00
commit bbb3ef9333
1861 changed files with 167960 additions and 0 deletions

View File

@@ -0,0 +1,11 @@
UniLay.cnf for Fly Dials
#[FlyD]
#02 ff00 1100 0000 0000 0000 0000 Dog's ear
#03 ff00 1200 0004 0004 0000 0000 Exit-button
#05 ff00 1200 0010 0010 0000 0000 Radio-button
#04 ff00 1200 0000 0000 0000 0000 Check-button
#06 ff00 1300 0000 0000 0000 0000 Underscored text (heading)
#07 ff00 1400 0000 0000 0000 0000 Group frame

Binary file not shown.

View File

@@ -0,0 +1,11 @@
ResourceMaster v3.64
#C 5@0@0@0@
#N 99@32@AZAaza___ _@AZAaza090___ _@@_@
#R 0@0@1@1@1@1@
#M 11010110@1181514052@7728@562@
#T 0@2@Tree000@@25@@
#T 1@2@Tree001@@1@@
#T 2@2@Tree002@@1@@
#T 3@2@Tree003@@1@@
#T 4@1@Tree004@@17@@
#c 9057@

Binary file not shown.

View File

@@ -0,0 +1,14 @@
in2rsm.rim v1.12 for Importing
******************************
IN2RSM is installed by copying "in2rsm.rim" into the "modules" folder
and entering it in the rsm.inf. What can be entered in "rsm.inf" is
listed below. The order of the entries determines the priority.
HRD-file:
#Fiin2rsm@HRD@hrd@HRD@ HRD-file@
RSO-file (RCS by Th.Otto)
#Fiin2rsm@RSO@rso@RSO@ RSO-file@

View File

@@ -0,0 +1,21 @@
static vars=TRUE
short file=FALSE
blank lines=TRUE
object numbers=TRUE
init te_ptext=TRUE
no init function=FALSE
init function=rs_init
exit function=rs_exit
ciconinit function=rs_ciconinit
ciconexit function=rs_ciconexit
optimize images=FALSE
optimize strings=TRUE
optimize icontext=FALSE
optimize substrings=FALSE
optimize emtystrings=TRUE
includes=
ob_spec=long
ub_code=long
ub_parm=long
draw function=mydraw
bi_pdata=int

Binary file not shown.

View File

@@ -0,0 +1,17 @@
rsm2cs.rem v1.0 for the export as C-sources
*******************************************
RSM2CS is installed by copying "rsm2cs.rem" and "rsm2cs.cnf" into the
"modules" folder and the following line is entered in rsm.inf:
#foC-Source@rsm2cs@1@c@h@@C-Sou[rce@1@
^ ^ ^
| | |
If a '0' is placed | | |
here, then the < | |
dialog appears only | |
when you press the | |
SHIFT key | |
| |
If other files (than *.c + *.h) are to be created, then the line must
be altered appropriately.

Binary file not shown.

View File

@@ -0,0 +1,38 @@
rsm2out.rem v1.95 for Exporting
*******************************
RSM2OUT is installed by copying "rsm2out.rem" to the "modules" folder
and registering it in rsm.inf.
Items that can be entererd in "rsm.inf" are listed below. The opening
square bracket determines the keyboard shortcut in the dialog.
HRD-file:
#foHRD@rsm2out@HRD@hrd@@@ H[RD-file@
C-Header-file:
#foC-Header@rsm2out@C-Header@h@@@ [C-Header@
Assembler:
#foAssem@rsm2out@Assem@s@@@ A[ssembler@
Modula:
#foModula@rsm2out@Modula@def@mod@@ [Modula@
Pascal:
#foPascal@rsm2out@Pascal@i@@@ [Pascal@
Fortran:
#foFortran@rsm2out@Fortran@inc@@@ [Fortran@
Omikron.BASIC:
#foOBasic@rsm2out@OBasic@lst@@@ OMICRON.[BASIC@
GFA-BASIC:
#foGBasic@rsm2out@GBasic@lst@@@ [GFA Basic@
HiSoft-BASIC:
#foHBasic@rsm2out@HBasic@bh@@@ H[iSoft Basic@
BGH-file (BubbleGEM Help file):
#FoBGH@rsm2out@BGH@bgh@@@ B[ubbleGEM HELP-file@

Binary file not shown.

View File

@@ -0,0 +1,44 @@
ResourceMaster v3.5
#C 12@0@0@0@
#N 99@12@AZAazA___ _@AZAaza090___ _@@_@
#R 0@0@2@1@2@1@
#M 0001011@1397179725@7728@501@
#T 0@1@MENU@@15@@
#O 7@28@ME_INFO@@
#O 9@28@ME_EDIT@@
#O 10@28@ME_SLIDER@@
#O 11@28@ME_TEXT@@
#O 12@28@ME_OBJECT@@
#O 14@28@ME_QUIT@@
#T 1@2@MAIN@@9@@
#O 2@26@MA_3D@@
#O 3@26@MA_ROUND@@
#O 5@21@MA_LIST@@
#O 6@21@MA_CIRC@@
#O 7@26@MA_MOD@@
#O 8@26@MA_EXIT@@
#T 2@2@TEXTWIN1@@4@@
#O 2@26@TE_ICONS@@
#O 3@26@TE_FONT@@
#T 3@2@ICONS@@13@@
#O 1@31@IC_FOLDER@@
#O 2@20@IC_POP@@
#O 3@28@IC_FIRST@@
#O 11@28@IC_LAST@@
#O 12@31@IC_BAR@@
#T 4@2@EDIT@@13@@
#T 5@2@TABS@@7@@
#O 1@26@RE_BUTTON1@@
#O 2@26@RE_RAHMEN1@@
#O 3@26@RE_RAHMEN2@@
#O 4@26@RE_BOXCHAR@@
#O 5@26@RE_TEXT@@
#O 6@26@RE_FRAME@@
#T 6@2@BUTTONS@@15@@
#T 7@2@FRAME1@@20@@
#T 8@2@FRAME2@@18@@
#T 9@2@BOXCHARS@@33@@
#T 10@2@TEXTS@@20@@
#O 19@29@TE_EDTEXT@@
#T 11@2@FRAME@@11@@
#c 5999@

View File

@@ -0,0 +1,36 @@
# Config-file for SysGem-Overlay for ResourceMaster from Version 3.0 on
# A hash introduces a comment. The rest of the line will be ignored.
# Empty lines are permitted as well.
# Enable3D switches the 3D-display on (1) or off (0).
# Works only if 16 colours or more are available.
Enable3D=1
# SysGem can draw buttons in two ways: Square-cornered (0) and
# slightly rounded (1).
UseRoundButtons=1
# Custom edit fields on (1) or off (0)
UseOwnEditFields=0
# Draw frames round edit fields (1) or not (0)
SetMonoEditFrame=0
# Thorsten Bergner on (1) or off (0)
IchbinThorsten=0
# The following values are available for colours:
# 0 = White, 1 = black, 2 = red, 3 = green, 4 = blue, 5 = cyan, 6 = yellow
# 7 = magenta, 8 = light grey, 9 = dark grey, 10 = dark red, 11 = dark green
# 12 = dark blue, 13 = dark cyan, 14 = dark yellow, 15 = dark magenta
# With this command you can determine in which colour the texts in the
# Frame-boxes is to be drawn.
FrameTextColor=2
# With this command you can determine in which colour the shortcuts
# are to be drawn.
ShortCutColor=2

Binary file not shown.

Binary file not shown.

View File

@@ -0,0 +1,50 @@
SysGem-Overlay v 0.04
=====================
This small program (sgemovl.ovl) is an overlay for ResourceMaster from
Version 3.0 on. With it it's possible to test the appearance of Resources
already while they are being created.
This overlay is written specially for the objects of the SysGem Library.
SysGem was programmed by Andreas Pietsch:
http://home.t-online.de/home/a.pietsch/
I, Gerhard Stoll, am responsible for the overlay. For this I have written
only a rump-program. Apart from this the original functions of SysGem are
used.
1. Installation
===============
1.1 RSM 3.0
-----------
Just copy the files "sgemovl.ovl" and "sgemovl.cnf" into the RSM "modules"
folder and rename them to "rsm.ovl" and "rsm.cnf".
1.2 RSM 3.2
-----------
Just copy the files "sgemovl.ovl", "sgemovl.cnf" und "sgemovl.rsc" into
the RSM "modules" folder.
2. Configuration
================
Besides the overlay itself there is also the file "sgemovl.cnf". There
the behaviour of the overlay can be set. More details will be found in
the commented file.
From RSM Version 3.2 onwards you can call up a configuration dialog. With
this various settings can be altered. In addition the overlay makes
available its own Toolbox for dialogs.
3. Problems
===========
When moving objects you may get some smearing.
4. Contact
==========
Gerhard Stoll @ LU (MausNet) - only mails below 16 KByte!

Binary file not shown.

View File

@@ -0,0 +1,11 @@
ResourceMaster v3.5
#C 5@0@0@0@
#N 99@12@AZAaza___ _@AZAaza090___ _@@_@
#R 0@0@2@1@2@1@
#M 1001011@0@7728@570@
#T 0@2@Tree000@@18@@
#T 1@2@Tree001@@5@@
#T 2@2@Tree002@@2@@
#T 3@2@Tree003@@1@@
#T 4@1@Tree004@@17@@
#c 10938@

Binary file not shown.

View File

@@ -0,0 +1,8 @@
ResourceMaster v3.5
#C 2@0@0@0@
#N 99@12@AZAaza___ _@AZAaza090___ _@@_@
#R 0@0@2@1@2@1@
#M 2001011@0@7728@570@
#T 0@2@Tree000@@24@@
#T 1@2@Tree001@@5@@
#c 32615@

View File

@@ -0,0 +1,76 @@
/*************************************************************
* *
* Examples for cicon_init() and cicon_exit() *
* Author: Armin Diedering *
* WWW: http://www.Diedering.de *
* *
*************************************************************/
#include <portab.h>
#include <gemfast.h>
/* Following functions are required */
WORD CountOfPlanes(); /* returns the number of planes of the */
/* current resolution */
WORD CanCicon(); /* gives info if the system can do CICONs */
WORD IsMagiC(); /* is MagiC the OS ? */
/* now we are off! */
long rs_ciconinit(CICONBLK *ciconblks, int ncib, OBJECT *objects, int nobj)
{
if(CanCicon())
{
if(IsMagiC())
{
while(ncib--) /* see rsm2cs.hyp */
{
CICON *cicon = ciconblks->mainlist;
CICON *found = cicon;
WORD planes = 0;
while(cicon) /* find suitable colour number */
{
if(cicon->num_planes <= CountOfPlanes()) /* can the OS handle this icon? */
{
if(cicon->num_planes > planes) /* are there more planes */
{ /* that I have found already? */
found = cicon;
planes = found->num_planes; /* I'll remember this */
}
}
cicon = cicon->next_res; /* next colour number */
}
ciconblks->mainlist = found; /* set found */
ciconblks++; /* next icon */
}
}
else
{
/* Here it gets complicated. One has to go through CICON by CICON. */
/* For this you first have to find and set a suitable colour number */
/* as for MagiC see above). Then the found image data, which are present */
/* in the standard format, have to be converted to the device-specific */
/* format. */
/* How this is to be achieved I'll leave to you! ;-) */
}
}
else /* the system can not handle CICONs */
{
while(nobj--) /* then convert all CICONs to ICONs */
{
if((objects->ob_type & 0xff) == G_CICON)
objects->ob_type = (objects->ob_type & ~0xff) | G_ICON;
objects++;
}
}
return(0);
}
void rs_ciconexit(long deskriptor)
{
}

View File

@@ -0,0 +1,11 @@
UniLay.cnf for Fly Dials
#[FlyD]
#02 ff00 1100 0000 0000 0000 0000 Dog's ear
#03 ff00 1200 0004 0004 0000 0000 Exit button
#05 ff00 1200 0010 0010 0000 0000 Radio button
#04 ff00 1200 0000 0000 0000 0000 Check button
#06 ff00 1300 0000 0000 0000 0000 Underscored text (Heading)
#07 ff00 1400 0000 0000 0000 0000 Group frame

Binary file not shown.

View File

@@ -0,0 +1,165 @@
Universal Overlay v1.2
----------------------
Armin Diedering
Last changed: 29.1.2000
Tab width: 3
1. What is UniLay ?
===================
UniLay is an overlay for ResourceMaster from Version 3.0 onwards. With
overlays it is possible to display user-defined objects already in the
editor.
UniLay uses ResourceMaster's own userdef-objects for this, which the
ResourceMaster uses when no MagiC special types are available. This has
the advantage that the overlay with its 2-3 kbyte is kept very small.
The disadvantage is that the objects are displayed in the editor not
quite the same as they will later look in the program. Nevertheless a
rough impression is possible.
2. Installation
===============
RSM 3.0:
--------
Simply copy the files "unilay.ovl" and "unilay.cnf" into the RSM
"modules" folder and rename them to "rsm.ovl" and "rsm.cnf".
RSM 3.2:
--------
Simply copy the files "unilay.ovl" and "unilay.cnf" into the RSM "modules"
folder. As RSM 3.2 supports multiple overlays, the files may be renamed
and UniLay copied several times into the "modules" folder. The filename
for the "*.ovl" and the "*.cnf" have to be identical (e.g. "flydials.ovl"
and "flydials.cnf").
From RSM 3.2 onwards an overlay can offer its own Toolboxes. UniLay looks
in the "modules" folder for a Tools-resource ("Overlay-Name.rsc"). This
Resource must be constructed in exactly the same way as an RSM Tool-
resource -> rsm.hyp.
3. Which objects are supported?
===============================
UniLay or the ResourceMaster currently supports 7 special objects:
- RSM_MOVEBUTTON The well-known dog-ear to make dialogs fly.
- RSM_BUTTON A button with an underscored character.
- RSM_CHECKBUTTON A check-button with/without underscored character.
- RSM_RADIOBUTTON A radio-button with/without underscored character.
- RSM_UNDERLINED An underscored string.
- RSM_GROUPBOX A group frame.
- RSM_NICELINE A niceline for menus.
Apart from RSM_MOVEBUTTON, the special objects only take effect when
dealing with G_STRING, G_BUTTON or G_TITLE objects.
For RSM_BUTTON, RSM_CHECKBUTTON and RSM_RADIOBUTTON the underscored
character will be marked with an opening square bracket in the button
text. Alternatively you can do it like MagiC by setting Whitebak; in that
case the position is determined by bits 8-11 of ob_states using a binary
format starting from none set for the first character, bit 8 (=1) set for
the second, bit 9 (=2) for the third, bit 8+9 (=3) for the fourth etc.
The MagiC method takes priority.
4. How do I configure UniLay?
=============================
UniLay loads in initialization the file "unilay.cnf". In this CNF-file
you can specify for which objects the overlay should be active.
The file has to commence with the following line!
------------Snip-----------
#[xxxx]
------------Snap-----------
This sets the ID of the overlay ("xxxx" represents any 4 characters). If
you want to (or must) use several CNF-files, then you should assign an ID
for each CNF. As the ID of the overlay is also saved in the *.rsm-file,
RSM will only activate the overlay if the IDs match.
To avoid conflicts with public overlays, private IDs should start with a
'_' such as "#[_AO1]" (Armins Overlay No.1).
Then follow the object lines.
Each valid object line is built up as follows:
------------Snip-----------
#00 0000 0000 0000 0000 0000 0000 Comment
------------Snap-----------
So the line always starts with a hash (double-cross). The hash is
followed by 7 hexadecimal-coded numbers, separated by a space. The
first always has 2 places and the rest four places. An optional comment
must be separated by spaces or tabs from the last number.
The first number determines the special object number. The following
apply:
0 -> DRAW_NOTHING
2 -> RSM_MOVEBUTTON
3 -> RSM_BUTTON
4 -> RSM_CHECKBUTTON
5 -> RSM_RADIOBUTTON
6 -> RSM_UNDERLINED
7 -> RSM_GROUPBOX
8 -> RSM_NICELINE
The folllowing 6 numbers are split into 3 pairs. Each number-pair
contains a mask and a comparison value. These number-pairs apply in each
case for the OBJECT-component type, Flags and States.
Example:
---------
1. The overlay should take over the display of an RSM_CHECKBUTTON when:
- The extended type = 22 (hex 16)
- The object type = G_STRING (28 or hex 1c)
#03 ffff 161c 0000 0000 0000 0000
--- ---- ---- -------------------
| | | |
| | | Flags and States are irrelevant
| | Ext.type=22 and Type=G_STRING?
| Use all bits of ob_type
RSM_CHECKBUTTON
2. As a checkbutton should only be draw when the EXIT-flag is not set,
we need a second line:
#00 ffff 161c 0004 0004 0000 0000
--- ---- ----
| | |
| | Is EXIT set?
| Only evaluate the EXIT-flag
DRAW_NOTHING
This line must be placed before the RSM_CHECKBUTTON-line.
3. An RSM_RADIOBUTTON should be drawn for the same conditions as above
when the RADIO-flag is set:
#04 ffff 161c 0010 0010 0000 0000
--- ---- ----
| | |
| | Is RADIO set?
| Only evaluate the RADIO-flag
RSM_RADIOBUTTON
This line too must be placed before the RSM_CHECKBUTTON-line but
after the DRAW_NOTHING line.
4. To summarize:
- The extended type = 22 (hex 16)
- The object type = G_STRING (28 or hex 1c)
- If EXIT-flag, then nothing should be drawn
- If RADIO-flag then RSM_RADIOBUTTON else RSM_CHECKBUTTON
------------Snip-----------
#00 ffff 161c 0004 0004 0000 0000 If Exit draw nothing
#04 ffff 161c 0010 0010 0000 0000 If RADIO -> RSM_RADIOBUTTON
#03 ffff 161c 0000 0000 0000 0000 If no EXIT and also no RADIO
then RSM_CHECKBUTTON
------------Snap-----------