---------- Original Message ----------
To: [oorexx:discussion] (408478@discussion.oorexx.p.re.sf.net)
From: Mark Miesfeld (miesfeld@users.sf.net)
Subject: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re: getTextSizeScreen
Date: 2014-05-30 10:22:00a
Hi Paul,
I just got back from an extended vacation yesterday at 1:00 pm. I'll get
this straightened out shortly, but it will take me a day or two to get
re-organized here.
But, real quickly. We know for sure you are picking up an old version of
the ooDialog class fie. Your error message says the error is on line 1363
of ooDialog.cls:
Error 90 running C:\Program Files (x86)\ooRexxOODIALOG.CLS line 1363:
External
name not found
Error 90.998: Unable to find external method "winex_getTextSizeScreen"
and that on that line it can't fine the external method mapping for
getTextSizeScreen. But, in the proper ooDialog.cls, the external mapping
is not on line 1363. As I showed you yesterday, line 1363 doesn't have
any relation to getTextSizeScreen
In the proper ooDialog.cls, the mapping for getTextSizeScreen is on line
7403:
So, for whatever reason, you are picking up a real old version of
ooDialog.cls. From the error message, I would say it is a 4.1 version of
ooDialog.cls.
To start to figure out the problem, look at your ooDialog.cls file and see
what is on line 1363.
Now, between ooDialog 4.1.0 and the current ooDialog there have been a lot
of changes. If you were using incorrect syntax, you may have a few
problems. But the problem you are showing with the error message does not
exist. We just need to figure out why you are picking up the wrong
version of ooDialog.cls.
I'll pick up your program sometime soon and run it. I'll be able to get
this straightened out soon.
--
Mark Miesfeld
On Fri, May 30, 2014 at 5:26 AM, Paul Higgins phigginsph99@users.sf.net
wrote:
Rick,
Already checked for that and to be sure I moved C:\Program Files
(x86)\ooRexx as the first file in the Path environment variable. Also
opened a CMD prompt and CD to C:\Program Files (x86)\ooRexx directory and
and moved the test.rex program there and it still failes.
Besides, why does V4.2 work when I go back to an older version of
oodialog?
By any chance are you running Windows 8 64 bit and oorexx V4.2 works?
Paul
---------- Original Message ----------
To: [oorexx:discussion] (408478@discussion.oorexx.p.re.sf.net)
From: Rick McGuire (bigrixx@users.sf.net)
Subject: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re: getTextSizeScreen
Date: 2014-05-30 7:04:09a
You likely have an older version of oodialog.dll somewhere on your path
that is getting picked up rather than the one that came with the
release.
Rick
On Fri, May 30, 2014 at 6:53 AM, Paul Higgins phigginsph99@users.sf.net
wrote:
Mark,
On the Windows 8 system I installed an older version of oodialog
(ooDialog-4.1.0.8276-x86_32.exe) and now the simple test program no
longer gets an error and my program GE2KAP.rex runs but does get a few
syntax errors that it never got before but generally seems OK. If I
install any of the V4.2 versions of oodiag (eg:
ooDialog-4.2.0.8276-x86_32.exe) I get the original error running the
test.rex :
Error 90 running C:\Program Files (x86)\ooRexx\OODIALOG.CLS line 1363:
External
name not found
Error 90.998: Unable to find external method "winex_getTextSizeScreen"
Paul
---------- Original Message ----------
To: [oorexx:discussion] (408478@discussion.oorexx.p.re.sf.net)
From: Paul Higgins (phigginsph99@users.sf.net)
Subject: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re:
getTextSizeScreen
Date: 2014-05-29 5:49:12p
Mark,
I get
ooDialog 4.2.3.9852
This test program is on Windows 8 64 bit running the 32bit version of
oorexx. I installed V4.2 on another computer running Windows 7 32 system
and the test program works that failed on WINDOWS 8 but I get a
different
error.
This program is used by hundreds of sailors around the world to create
charts from Google Earth. It works fine on oorexx before V4.2.
If you execute GE2KAP.EXE it fails with a RC=88 trying to invoke
GE2KAP.REX. If you invoke GE2KAP.REX directly it fails on a ADDCHECKBOX.
Paul
---------- Original Message ----------
To: [oorexx:discussion] (408478@discussion.oorexx.p.re.sf.net)
From: Mark Miesfeld (miesfeld@users.sf.net)
Subject: [oorexx:discussion] Re: [oorexx:discussion] Re:
getTextSizeScreen Date: 2014-05-29 5:05:38p
On Thu, May 29, 2014 at 1:22 PM, Paul Higgins
phigginsph99@users.sf.netwrote:
Mark,
Even with just ooDialog.cls it gets the same error and another user of my
program gets the same. I have uninstalled completely even deleted the
directory then reinstalled, same thing. Are you using Windows 8?
Here is program and output again.
~~~~
exit 8
::requires ooDialog.cls
C:\PCOMM>test.rex
1363 - ::method getTextSizeScreen external "LIBRARY oodialog
winex_getTextS
izeScreen"
2 - ::requires ooDialog.cls
Error 90 running C:\Program Files (x86)\ooRexxOODIALOG.CLS line 1363:
External
name not found
Error 90.998: Unable to find external method "winex_getTextSizeScreen"
Hi Paul,
The ooDialog that ships with ooRexx 4.2.0 is ooDialog 4.2.3. You can run
the oodialog executable to see what version it is. You should get:
C:\work.ooRexx>oodialog -v
ooDialog 4.2.3.9852
C:\work.ooRexx>
But you won't. On line 1363 of ooDialog.cls:
::method begin
expose width height
use strict arg
self~calcSizes <===== Line 1363
if self~createCenter(width, height, self~captionText) then do
self~popup('ShowTop')
ret = 0
end
So, for some reason you don't have ooDialog installed correctly. If you
installed ooRexx 4.2.0 and you were sure the old version was completely
removed, then it seems like you have an ooDialog.cls file somewhere in
the path that is getting picked up by mistake.
Okay, that's your problem. That is the incorrect version of the
ooDialog.cls file. It is from the 4.1.0 version of ooDialog.
I don't know how you got the ooDialog versions scrambled up. Possibly ...
well I don't really know. If I were you I would run the ooRexx uninstall
program by itself. When it finishes, go to the command line and completely
delete the ooRexx directory. You will need to use the 'run as'
administrator. Then re-install ooRexx 4.2.0.
I would look in the 64-bit program directory before you re-install and
double check there is not any ooRexx files in that directory.
Other people have installed ooRexx on Windows 8 and 8.1 and have reported
no problems. So, I think the install program is okay.
What I think is that you will still have the same syntax problems you had
when you tried installing on Windows 7. But, those should be easy to take
care of.
Let me know how it goes.
--
Mark Miesfeld
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mark,
At line 1363 of the ooDialog.cls that is in C:\Program Files (x86)\oorexx has:
::method getTextSizeScreen external "LIBRARY oodialog winex_getTextSizeScreen"
Paul
---------- Original Message ----------
To: [oorexx:discussion] (408478@discussion.oorexx.p.re.sf.net)
From: Mark Miesfeld (miesfeld@users.sf.net)
Subject: [oorexx:discussion] Re: [oorexx:discussion] Re: [oorexx:discussion] Re:
[oorexx:discussion] Re: [oorexx:discussion] Re: getTextSizeScreen
Date: 2014-05-30 10:22:00a
This e-mail was delivered via satellite phone using GMN's XGate software.
Please be kind and keep your replies short.
On Fri, May 30, 2014 at 8:39 AM, Paul Higgins phigginsph99@users.sf.net
wrote:
Okay, that's your problem. That is the incorrect version of the
ooDialog.cls file. It is from the 4.1.0 version of ooDialog.
I don't know how you got the ooDialog versions scrambled up. Possibly ...
well I don't really know. If I were you I would run the ooRexx uninstall
program by itself. When it finishes, go to the command line and completely
delete the ooRexx directory. You will need to use the 'run as'
administrator. Then re-install ooRexx 4.2.0.
I would look in the 64-bit program directory before you re-install and
double check there is not any ooRexx files in that directory.
Other people have installed ooRexx on Windows 8 and 8.1 and have reported
no problems. So, I think the install program is okay.
What I think is that you will still have the same syntax problems you had
when you tried installing on Windows 7. But, those should be easy to take
care of.
Let me know how it goes.
--
Mark Miesfeld