Comet dialog commands


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]

Posted by Grant Foraker on June 25, 2009 at 15:08:09:

1) Found this the other day and it works :)

My ListView programs, developed in Visual Studio, only highlighted the first column. Couldn't find a setting in VS to do what I wanted.

So, now I add ..

cosState = True
GOSUB COS.ListViewFullRowSelect

and the highlight will span the whole row. A command that explains itself. Go figure :)

2) early on, I decided to add my DLL's files to the QDIR as TXT files. Lets me know about date/time stamp etc.

a) advantage - you can use DOSCOPY (option 32) to copy the DLL's out of Comet for delivery. Back in at the destination.

b) disadvantage - you can't use COPY (option 4). It treats the DLL as if it were a true TXT file and corrupts the destination file. same for CometEx.

c) new advantage - in Brian's original examples he does a PSTAT(PARTITION) to determine the DIR where the DLL is located. Meaning the DLL has to be in the same directory as the OBJ. And, no QDIR entry is required. This worked fine for me until recently. I found the need to develop OBJ's in a separate DIR. This meant that everytime I rebuilt a DLL I had to do a second copy to the development DIR. Bewilderment when I forgot :)

So, I'm now using SUB(FSTAT(cosDllName$),3,3) and letting the QDIR give me the DIR of the DLL.

Works for me :)


Follow Ups:



Post a Followup

Name:
E-Mail:

Subject:

What is the name of the main Signature System's Product?  

Comments:

Optional Link URL:
Link Title:
Optional Image URL:

You may attach up to 5 files to your followup (see below):





Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ]