Re: Questions About XyWin

[SysOp]

Robert, each of the examples you provided relate to keys which are *Windows*
keys (or functions). We do not have control of the hardware with our Windows
version. Only in cases where keys are not specifically Windows keys can we map
a XyWrite function. With this in mind we had to remap our wildcard functions to
TABLE=CTRL+ALT. I spoke with Development with respect to this issue as well.
It was explained to me that because this is a Windows product, the product
conforms to Windows conventionality. There is a particular *resource* file
which would allow our product to remap keys under windows, but this would have
to be coded into the product. This would deviate from Windows conventions and
therefore it was not chosen as the course of development. The problem with the
ALT=SHIFT keys is directly related to this convention. When the ALT key is
pressed (whether alone or in combination with another control key), Windows has
control of that key and it is not passed to our program for control.

Your point #3 can be replicated. I will forward a bug report in your name
today.

Point #4 - We have no control of this, it is under the control of Windows. We
have had requests from some publishers to allow control of the filename
displayed (i.e. alias names), however we cannot remove this.

Point #5 - Correct, the BK default is broken. We currently set the default in
the XW.EXE to "1" and the XWSET.DFL has a value of "0". We plan to set the
default in XW.EXE to "0" instead. When this release is ready I will post notice
here for you. We are not making this change only because the default is broken,
we feel that there could be serious problems related to overwritten files with
a value of "1".

Point #6 - Maybe I do not understand the question concerning C-Frames, but we
have the same C-Frames in XWDLG.DLG as in XY$.DLG?? Again, the Type L frames
are linked in with Windows. I think you are right that K-Frames would be the
best alternative.

Point #7 - These functions were removed, although you can find reference in the
.DLG file. The code in the .DLG file remains only due to the fact that the
Development menus maintain code from previous versions in some cases. This
process was first started when we were developing international versions of
Signature. The Windows Menu (SW) was removed specifically because the "Window"
pulldown provides all of the windows and the sizing stuff is linked in with
Windows conventions.

To be candid, a lot of the things which are easily done in III Plus and XY4 are
done in a different fashion due to the fact that this is a Windows program.
When conforming to Windows conventionality, a certain amount of flexibility is
compromised.

SysOp