Detect DDT or SDK was used?

[Cliff Nichols]

I am going over old code, and found a "minor inconvenience" that I had mixed and matched DDT with SDK code for a window. (nice example of a "no-no" though ) so it got me wondering. Is there a way to tell if I used DDT or SDK at runtime?

[Michael Mattias]

At runtime?

$USING_DDT =  "YES" 

FUNCTION PBMAIN
   PRINT USING$( "USING DDT: &", $USING_DDT) 
...

Besides, "Mixing SDK and DDT" is not ALWAYS "bad" or "wrong"

What IS always "bad" or "wrong" is using DDT commands against windows or controls not created with DIALOG NEW or CONTROL ADD.

But since both CBHNDL and the "hCtrl" returned by CONTROL HANDLE are valid window handles (this is documented), the use of API calls against them is permitted.

MCM

[Cliff Nichols]

Sooooo, using Windows API (SDK) commands on something that may have been created DDT is not wrong or bad????

But using DDT commands or PB assist on something that was created API MIGHT be bad???

that is the confusion I have often seen, asked, answered, asked again....

I am seeing the "Application Specific veil" but its a lonngggg idea, and hard to overcome what I know as "Set in Wet Concrete"

[Dave Biggs]

http://www.powerbasic.com/support/pbforums/showthread.php?p=304004#post304004

Actually, DDT controls were never, ever designed nor intended for use with non-DDT windows and dialogs.
If you break "the rules", you are guaranteed to have a problem at some point.
There has been "no change" in this regard, so PowerBASIC recommends that you consider it carefully.

Conversely, the opposite is perfectly acceptable.
Once you have a Windows Handle from a DDT operation, you are encouraged to use it in WinAPI functions
like GetWindowLong(), etc. This expands your capabilities a great deal, with very little "risk".

Best regards,

Bob Zale
PowerBASIC Inc.

[jcfuller]

. Is there a way to tell if I used DDT or SDK at runtime?

GetClassName

James

[Patrice Terrier]

#32770