forums.silverfrost.com

LitusSaxonicum

Not really much of a problem, but if a crosshair cursor crosses an area filled with RGB (127,127,127) it disappears, probably because XORing mid grey with the cursor line colour gives you mid grey.

Visually it gives you the odd effect that looks as though the mouse pointer crosshair went under the filled area.

Eddie

PaulLaidler · Posted: Tue Jul 14, 2015 7:05 am Post subject:

Eddie

I am not clear about whether or not you are requesting a fix.
After that it will be a question of who provides the cross-hair and who provides the grey background.

a) the user
b) ClearWin+ or
c) Microsoft

Wilfried Linder · Posted: Tue Jul 14, 2015 9:26 am Post subject:

I use a crosshair in black with a one-pixel border in white. A collection of cursors is available in c:\windows\cursors.

Wilfried

LitusSaxonicum · Posted: Tue Jul 14, 2015 11:47 am Post subject:

Hi Paul,

No fix needed or expected for my original post. This was simply an observation of behaviour that surprised me until I thought about it. The answer was that it was my grey area and my cursor, programmed in Clearwin+.

The scenario is that the user picks first an object, then a coordinate within that object. The object selection is done with an elaborate cursor, and once an object is selected the cursor changes to a crosshair so that the resolution becomes one pixel.

I thought that I'd write a very simple demonstrator for the effect, as the default cursor in a %gr area is a small 1-pixel crosshair, viz:

LitusSaxonicum · Posted: Tue Jul 14, 2015 11:51 am Post subject:

And Wilfried, thanks. I hadn't forgotten, but I haven't got round to thinking about whether it needs a change or not, or indeed, if it is a significant problem.

Eddie

LitusSaxonicum · Posted: Fri Jul 17, 2015 12:02 pm Post subject:

So nobody cares that COLOUR= is not a valid option, or that VGA_COLOURS has reverted to being the default in v7.20?

I suppose I don't care much either, as I never used COLOUR= before, and all my programs started life when VGA_COLOURS was the default!

Eddie

Wilfried Linder · Posted: Fri Jul 17, 2015 2:19 pm Post subject:

Eddie, I always use constructions like

PaulLaidler · Posted: Fri Jul 17, 2015 5:01 pm Post subject:

Eddie

I was not aware of a regression. Are you sure that you have used the latest DLL?

LitusSaxonicum · Posted: Fri Jul 17, 2015 6:12 pm Post subject:

Paul,

You are right - I thought I was safe, with a brand new laptop and a first time install of the PE, but my editor was pointing at a USB stick and it was on there. I half expected to be told by someone that their installation didn't throw the error, but there you go.

Next time, I'll add IMPLICIT_NONE and never get a problem!

A useful addition sometime might be a routine:

DONT_RUN_WITH_SALFLIBC_OLDER_THAN@ (Number)

And maybe if Number = 0, then it is equivalent to specifying the version of Salflibc.dll that matches the FTN95.EXE in use (or later).

Anyway, did you see the effect with the cursor? Interesting. I'm going to investigate other cursors along with Wilfried's suggestion. I've already used custom cursors in a number of places.

Eddie

PaulLaidler · Posted: Fri Jul 17, 2015 8:08 pm Post subject:

Eddie

I did not see the effect but I know exactly what you mean.

Wilfried Linder · Posted: Sat Jul 18, 2015 8:46 am Post subject:

Eddie, I've also had some troubles with a non-actual version of the SALFLIBC.DLL. Therefore, all times when I get a new DLL version I update the number in the following code which I use at the beginning of every program:

LitusSaxonicum · Posted: Sat Jul 18, 2015 6:18 pm Post subject:

Wilfried,

Thanks - I was sure there was a routine out there somewhere. I don't see why FTN95 shouldn't lock the relevant version number into the executable, but that's probably undesirable for reasons I don't know about. In answer to having to change that version number each time you upgrade FTN95, surely you don't have to, because it is the minimum version number it will run with. In any case, your software has its own version number and you have to update that, don't you?

I've found various things in my collection of cursors that do show against a background of RGB@(127,127,127). The problem of looking in the \windows\cursors subdirectory is that they are different in different versions of Windows, so there are a lot, and choosing particular ones to put in my RESOURCES is going to need some experimentation.

As for /undef, I thought the answer was IMPLICIT NONE!

Eddie