forums.silverfrost.com

PaulLaidler · Posted: Tue Dec 03, 2019 7:54 am Post subject:

It's good that it is now working for you although it can't have anything to do with the INCLUDE files.

I was going to suggest that you try using %if. This causes the following control to have the initial focus when the Window is opened.

LitusSaxonicum · Posted: Wed Dec 04, 2019 10:40 am Post subject:

A problem that appears 'out of the blue' and then disappears, equally mysteriously, after a fresh recompile is a difficult one to track down, and wastes a lot of time looking for the reason, which may never be found. From my own experience, there are at least a couple of causes that are worth checking against.

One is the use of a variable that has not been properly initialised - but it needs to be one that isn't very important, or the error may be experienced after a recompile. Another reason is when you link in a superseded version of one or more routines, usually by accident and a misspelling of a path.

However, the one that really got me some years ago and led to me writing a post entitled 'When is a handle not a handle' was a misunderstanding of what a handle is when applied to a Clearwin+ graphics area. For most controls in a Windows application that have a handle, this is allocated by Windows, and CW+ simply reports it back. CW+ graphics areas need to be provided with a handle - or did. This applies to %gr and %pl. If you assume, wrongly, that a handle is passed back, then you will get anything that resides in the handle variable when the program runs. Needless to say, this makes moving between graphics areas quite difficult, as in some cases they may even have the same value for the handle.

Paul did some work on this (see items 407 and 408 in cwplus.enh) but my bet is on this as a cause. To get a handle passed back you need to give the option [handle]. But it never hurts to assign the user-supplied handle and work that way.

Eddie

John-Silver · Joined: 30 Jul 2013 Posts: 1381 Location: Aerospace Valley

Paul wrote:

PaulLaidler · Posted: Thu Feb 27, 2020 4:40 pm Post subject:

The original error message described at the start of this thread has now been changed. In future you will get a warning that the routine has already been declared.