View previous topic :: View next topic |
Author |
Message |
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2388 Location: Yateley, Hants, UK
|
Posted: Fri Jan 21, 2011 5:29 pm Post subject: |
|
|
"It" being the Clearwin+ guide.
Seems like the text is there already, just the Figures aren't online. Can I make the suggestion that some of the illustrations are regenerated with 1 24 default.manifest as well as in raw form? This would show Clearwin+ off rather better.
Eddie |
|
Back to top |
|
|
jjgermis
Joined: 21 Jun 2006 Posts: 404 Location: Nürnberg, Germany
|
Posted: Fri Jan 21, 2011 5:38 pm Post subject: |
|
|
Uploaded with ImageShack.us |
|
Back to top |
|
|
Vladimir
Joined: 22 Nov 2006 Posts: 11
|
Posted: Sat Jan 29, 2011 10:43 pm Post subject: ClearWin+ problems |
|
|
Some problems with ClearWin+, mostly with documentation.
1. There is a logical function BROWSE_FOR_FOLDER@. Yes, it does work! But only for existing folders, you couldn't add a new folder (as in standard Windows dialog). Why?
2. Help file says that you can use SET_BROWSE_FOR_FOLDER_INITIAL@ subroutine to provide an initial PATH for function BROWSE_FOR_FOLDER@ (on the page describing this function), but no details are given. My attempts were as this:
Code: | SET_BROWSE_FOR_FOLDER_INITIAL@(init) |
The answer from FTN95:
Quote: | *** Statement not recognised |
More funny result was with this arrangement:
Code: | res = SET_BROWSE_FOR_FOLDER_INITIAL@(init) |
The answer was:
Quote: | *** SET_BROWSE_FOR_FOLDER_INITIAL@ is a SUBROUTINE so cannot be used as a |
Well, he is cheating! He does know what SET_BROWSE_FOR_FOLDER_INITIAL@ is, but deliberately lies! It seams that this subroutine is dropped...
That's not all my problems, but I am struggling with the rest of them and hope to find some idea to solve. |
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2388 Location: Yateley, Hants, UK
|
Posted: Sun Jan 30, 2011 12:30 am Post subject: |
|
|
Vladimir,
Did you forget the "CALL"? (It happened to me earlier today!)
The routine works for me:
Code: | CHARACTER*(129) PATH(4), PROMPT
LOGICAL DIDIT
PATH(1)='C:\WINDOWS\'
CALL SET_BROWSE_FOR_FOLDER_INITIAL@ (PATH(1))
PROMPT = 'Select default folder for datafiles'
DIDIT = BROWSE_FOR_FOLDER@ (PROMPT,PATHWAY)
IF (DIDIT) PATH(1) = PATHWAY |
... so I'm confident that it works.
You might also find this useful. Get the program location with:
Code: | CHARACTER*(129) PNAME
CALL GET_PROGRAM_NAME@ (PNAME)
CALL UPCASE@ (PNAME)
N = LEN_TRIM (PNAME) |
then you take the EXE name off the end of the string, and you have the path to your application's folder! (You need this sometimes if the program is started from a file association when you click on a data file. In this case, the working directory is not where the program is stored).
Edit 1: I've never added a folder, but there is a routine MKDIR@ (see in the FTN95 library, File manipulation routines). You may need ATTACH@ and CURDIR@ as well.
Eddie |
|
Back to top |
|
|
Vladimir
Joined: 22 Nov 2006 Posts: 11
|
Posted: Sun Jan 30, 2011 8:45 am Post subject: |
|
|
LitusSaxonicum
Shame on me! My brains were out yesterday night! Yes, it works! |
|
Back to top |
|
|
Vladimir
Joined: 22 Nov 2006 Posts: 11
|
Posted: Sun Jan 30, 2011 9:56 pm Post subject: |
|
|
Nevertheless, one more question. This is strictly about documentation. FTN95 help file says that it you can use dialog resources with winio@ %di format code. And %di is not documented in the help file. "Getting started" section in "Using dialog resources" chapter says that the sample in the subdirectory clearwin\di\s1Start can help in understanding this format. But in my FTN99 Express installation there is no subdirectory "di" in the Examples folder! A lot of important, but minor problems are discussed in the chapter mentioned, but no complete picture is given. You are not instructed how you should bring all these peaces together to make them work. At least I didn't understand it. |
|
Back to top |
|
|
Robert
Joined: 29 Nov 2006 Posts: 445 Location: Manchester
|
|
Back to top |
|
|
Vladimir
Joined: 22 Nov 2006 Posts: 11
|
Posted: Mon Jan 31, 2011 6:59 am Post subject: |
|
|
Robert
You are right, but there are exactly the same things as in the help file. With the same problem.
Let us imagine that you want to make zombie in a kind of Voodoo cult. You can paint this zombie by resource editor, and you know that you need some extra stuff to make him alive: ash of a hanged man, windows.h header file, black cat, and so on. The documentation about %di format tells the user a lot of valuable things. You can get knowledge on making this zombie responsible for some of you commands, but you can not get an idea how to make him alive first! |
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2388 Location: Yateley, Hants, UK
|
Posted: Mon Jan 31, 2011 4:08 pm Post subject: |
|
|
I can't follow the instructions on %di either, so I gave up. I have a sneaking feeling that I would like to use %di, if only I was able to.
To stretch the zombie analogy further, you need to give the incantations in Creole, so even the French we learnt at school isn't much help. If you did Latin, you are even less able to comprehend. Very frustrating, while all around in the forum there are dozens of people who can rattle the bones, mutter juju, and make the forces of Clearwin+ work together like the dancers in Michael Jackson's "Thriller".
E |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7928 Location: Salford, UK
|
Posted: Wed Feb 02, 2011 12:00 pm Post subject: |
|
|
Have you seen the set of samples in the installed examples....
Documents\FTN95 Examples\clearwin\di |
|
Back to top |
|
|
|