View previous topic :: View next topic |
Author |
Message |
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2390 Location: Yateley, Hants, UK
|
Posted: Tue Apr 18, 2017 10:13 am Post subject: |
|
|
Beat me to it, Simon.
Clearwin.enh is in the installation 'Docs' folder: the online version may be the latest one, and if you don't have the latest compiler release, then there may be a point of two of difference.
Eddie |
|
Back to top |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2390 Location: Yateley, Hants, UK
|
Posted: Fri Apr 21, 2017 9:34 am Post subject: |
|
|
John,
You are reading a bit of documentary archaeology! The Supplement is the Clearwin+ Fortran Edition manual. The latter evolved through several versions from the former. Simon's suggestion of looking in the .ENH file was for a source of additional info.
Eddie |
|
Back to top |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
Posted: Tue Apr 25, 2017 1:50 am Post subject: |
|
|
Update of the documentation from 'Clearwin+ Users Supplement' to 'Clearwin+ Fortran Edition manual.' everywhere in the on-line (and maybe other versions) manual(s) should be a piece of cake for Paul then. |
|
Back to top |
|
|
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Tue Apr 25, 2017 11:40 am Post subject: |
|
|
Hello,
one more remark concerning the symbol
DRAW_TEXT@
for which the numbers of parameters changed from 4 to 5 (compiler WARNING - SUBROUTINE DRAW_TEXT@ has been called with too few arguments).
I do not know the interface for the "new" routine DRAW_TEXT@, however I have learnt that I could use DRAW_CHARACTERS@ instead from one of the pdf files mentioned above.
Maybe it is worthwhile knowing the interface of the "new" DRAW_TEXT@ , too.
Regards,
Dietmar |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7934 Location: Salford, UK
|
Posted: Tue Apr 25, 2017 3:50 pm Post subject: |
|
|
Dietmar
I think that there are two things that need fixing here.
1) dbos.ins needs changing to
Code: | C_EXTERNAL DRAW_TEXT@ "__win_draw_text"(INSTRING,REF,REF,REF)
|
2) __win_draw_text is not exported correctly from clearwin64.dll.
It should have four arguments. The recommended change is to use DRAW_CHARACHERS@ instead.
You could change dbos.ins but I think that DRAW_TEXT@ will still fail because of (2). |
|
Back to top |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
Posted: Tue Apr 25, 2017 7:35 pm Post subject: |
|
|
DRAW_CHARACTERS@
... unless it's for a new french syntax version of ftn95 that's 'dear' to the heart or 'expensive' ! lol |
|
Back to top |
|
|
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Thu Apr 27, 2017 11:18 am Post subject: |
|
|
Yes,
I have substituted DRAW_TEXT@ by DRAW_CHARACTERS@ in my GUI app code and this worked fine
For those who are interested:
in a remark which I made previously in this post I wondered that a small example containing symbol GET_WKEY1@ could be compiled/linked using ftn95/slink64, our big GUI example, however, left symbol GET_WKEY1@ unresolved.
Although meanwhile this problem is solved, I found that you use character " in C_EXTERNAL definitions of file dbos.ins (ftn95 Version 8.10). When I looked at file clearwin.ins of ftn95 Version 7.10 I saw that C_EXTERNAL definitions of file clearwin.ins used character ' instead. What was the reason for this?
Regards
Dietmar |
|
Back to top |
|
|
PaulLaidler Site Admin
Joined: 21 Feb 2005 Posts: 7934 Location: Salford, UK
|
Posted: Thu Apr 27, 2017 12:41 pm Post subject: |
|
|
There is no reason for this. You can use either single or double quotes.
Perhaps clearwin.ins was written when FTN77 was still in use.
dbos.ins was written within the last few months and double quotes was just a random choice. Hopefully, if there are any FTN77 users still around then they won't be porting to 64 bits. |
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2390 Location: Yateley, Hants, UK
|
Posted: Thu Apr 27, 2017 3:19 pm Post subject: |
|
|
In real life, double quotes allow you to avoid confusion when using the apostrophe for the Saxon Genitive or word contractions without ambiguity.
In programming, being able to use single or double quotes enables use of the other in character strings , but degrees, minutes and seconds are still difficult, as in:
(similar for feet and inches)
Still not simple, especially when reading it years after writing the code.
Using both types of quotes is one of the things a committed Fortran-77 user is most likely to pick up and adopt, along with inline comments. |
|
Back to top |
|
|
John-Silver
Joined: 30 Jul 2013 Posts: 1520 Location: Aerospace Valley
|
Posted: Thu May 04, 2017 10:48 pm Post subject: |
|
|
a very astute angle on the subject from a saxon (as would be expected !)
how would a 'double-singlequote' be formatted ?
"''"
or
"'","'" |
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2390 Location: Yateley, Hants, UK
|
Posted: Fri May 05, 2017 9:43 am Post subject: |
|
|
It depends if it is a character constant or in a format statement.
"'","'" will only work in a format statement, and would have to be "'"//"'" in a character - this would work in a format statement too.
I think that "''" would work anywhere, as it is the first character that must be matched to the end of the string.
The apostrophe is also a key part of the Saxon Genitive.
Can I have this month's award for pedantry please?
Eddie |
|
Back to top |
|
|
mecej4
Joined: 31 Oct 2006 Posts: 1892
|
Posted: Fri May 05, 2017 1:27 pm Post subject: Re: |
|
|
LitusSaxonicum wrote: |
The apostrophe is also a key part of the Saxon Genitive.
Can I have this month's award for pedantry please?
Eddie |
A fitting reward would be a plaque, engraved with Latin text that is unblemished by punctuation, a la https://i.stack.imgur.com/lMmJi.jpg . |
|
Back to top |
|
|
DietmarSiepmann
Joined: 03 Jun 2013 Posts: 279
|
Posted: Tue Jun 12, 2018 4:55 pm Post subject: |
|
|
There is another unresolved symbol which I found when linking a 64 bit GUI application, namely
Code: |
DELETE_POLYGON_DEFINITION@
|
I wonder how to get rid of this symbol. The code sequence to create/delete the polygon is
Code: |
CALL CREATE_POLYGON@ (...)
CALL FILL_POLYGON@(...)
CALL POLYLINE@(...)
........
CALL DELETE_POLYGON_DEFINITION@(...)
|
All 4 subroutines are listed in the ClearWin+ documentation Appendix A, Functions ported from DBOS, Graphics, but only the last is marked as undefined by slink64. I know there are alternate routines, however, I wonder, how to set parameter 4 of DRAW_FILLED_POLYGON@ which is the alternate routine to DELETE_POLYGON_DEFINITION@ (which specifies the fill color using the current color mode).
Thanks for any help.
Regards,
Dietmar |
|
Back to top |
|
|
LitusSaxonicum
Joined: 23 Aug 2005 Posts: 2390 Location: Yateley, Hants, UK
|
Posted: Tue Jun 12, 2018 11:15 pm Post subject: |
|
|
Dietmar, the 4th parameter for DRAW_FILLED_POLYGON@ is an integer created with a call to RGB@. I only use Win32, so it's an INTEGER*4. You call RGB@ with 3 parameters: the Red, Green and Blue components, each described with an integer in the range 0...255. RGB mode, with 24-bit colour is the default in Clearwin these days, no longer the 16 colour VGA mode.
You can specify 'ICOL' as in the documentation using say:
ICOL = RGB@ (0, 0, 0) (for black)
or just put it in the subroutine call, as in:
CALL DRAW_FILLED_POLYGON@ (IX, IY, N, RGB@(127, 127, 127) ) (grey)
You really need to update your codes to use the 'post-DBOS' graphics to future proof them.
Eddie |
|
Back to top |
|
|
|