From: Staffan T. <sta...@gm...> - 2013-10-29 17:49:20
|
After a lot of research (and swearing) I've managed to compile ooDialog and ooSQLite using VS 2012 with SP3 installed to support XP as target system. The compiles run with no apparent problems. And the resulting load modules run as expected on my Win7 system. But when I try it all on my older XP system it fails with the following: AppName ooDialog.exe AppVer: 4.2.4.9490 ModName: rexxapi.dll ModVer: 4.1.3.9341 Offset: 00001efa ooRexx is not preinstalled on my XP system so I carry over all of the following from the Win7 system to the XP system together with my app: orexxole.dll rexx.dll rexx.exe rexx.img rexxapi.dll rexxutil.dll rxapi.exe rxwinsys.dll ooDialog.cls ooDialog.com oodialog.dll ooDialog.exe oodPlain.cls oodWin32.cls ooSQLite.cls oosqlite.dll ooSQLite3.exe Doing the same to another Win7 system without a preinstalled ooRexx works fine. So there seems to be some sort of incompatibility introduced between ooDialog and ooRexx that has been caused by the new compile. To activate the XP support in VS 2012 with SP3 I had to add the following before running the vcvarsall.bat: @set INCLUDE=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Include;%INCLUDE% @set PATH=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Bin;%PATH% @set LIB=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Lib;%LIB% @set CL=/D_USING_V110_SDK71_;%CL% @set LINK=/SUBSYSTEM:CONSOLE,5.01 %LINK% @"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" I suspect CL= and/or LINK= is causing this but I'm unable to say why. And btw, all of the above is 32-bit. A helpful hand is appreciated. Staffan |
From: Mark M. <mie...@gm...> - 2013-10-29 18:10:12
|
It's hard to say Staffan. What happens if you leave ooDialog.exe out of the picture? Just run an ooDialog program through rexx.exe. For example, go to the the examples directory and: rexx.exe animalGame.rex -- Mark Miesfed On Tue, Oct 29, 2013 at 10:48 AM, Staffan Tylen <sta...@gm...>wrote: > After a lot of research (and swearing) I've managed to compile ooDialog > and ooSQLite using VS 2012 with SP3 installed to support XP as target > system. The compiles run with no apparent problems. And the resulting load > modules run as expected on my Win7 system. But when I try it all on my > older XP system it fails with the following: > > AppName ooDialog.exe > AppVer: 4.2.4.9490 > ModName: rexxapi.dll > ModVer: 4.1.3.9341 > Offset: 00001efa > > ooRexx is not preinstalled on my XP system so I carry over all of the > following from the Win7 system to the XP system together with my app: > > orexxole.dll > rexx.dll > rexx.exe > rexx.img > rexxapi.dll > rexxutil.dll > rxapi.exe > rxwinsys.dll > ooDialog.cls > ooDialog.com > oodialog.dll > ooDialog.exe > oodPlain.cls > oodWin32.cls > ooSQLite.cls > oosqlite.dll > ooSQLite3.exe > > Doing the same to another Win7 system without a preinstalled ooRexx works > fine. So there seems to be some sort of incompatibility introduced between > ooDialog and ooRexx that has been caused by the new compile. > > To activate the XP support in VS 2012 with SP3 I had to add the following > before running the vcvarsall.bat: > > @set INCLUDE=%ProgramFiles(x86)%\Microsoft > SDKs\Windows\7.1A\Include;%INCLUDE% > @set PATH=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Bin;%PATH% > @set LIB=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Lib;%LIB% > @set CL=/D_USING_V110_SDK71_;%CL% > @set LINK=/SUBSYSTEM:CONSOLE,5.01 %LINK% > @"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" > > I suspect CL= and/or LINK= is causing this but I'm unable to say why. And > btw, all of the above is 32-bit. > > A helpful hand is appreciated. > > Staffan > > > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Mark M. <mie...@gm...> - 2013-10-29 18:19:05
|
Staffan, You most likely need to build ooRexx with the same procedure as you built ooDialog and ooSQLite to have a chance for it to work. Who knows what: @set CL=/D_USING_V110_SDK71_;%CL% causes the compiler and linker to do. Using the ooRexx binaries built by an older compiler version, on the face of it, seems likely to fail. -- Mark Miesfeld On Tue, Oct 29, 2013 at 11:10 AM, Mark Miesfeld <mie...@gm...> wrote: > It's hard to say Staffan. > > What happens if you leave ooDialog.exe out of the picture? Just run an > ooDialog program through rexx.exe. For example, go to the the examples > directory and: > > rexx.exe animalGame.rex > > -- > Mark Miesfed > > > On Tue, Oct 29, 2013 at 10:48 AM, Staffan Tylen <sta...@gm...>wrote: > >> After a lot of research (and swearing) I've managed to compile ooDialog >> and ooSQLite using VS 2012 with SP3 installed to support XP as target >> system. The compiles run with no apparent problems. And the resulting load >> modules run as expected on my Win7 system. But when I try it all on my >> older XP system it fails with the following: >> >> AppName ooDialog.exe >> AppVer: 4.2.4.9490 >> ModName: rexxapi.dll >> ModVer: 4.1.3.9341 >> Offset: 00001efa >> >> ooRexx is not preinstalled on my XP system so I carry over all of the >> following from the Win7 system to the XP system together with my app: >> >> orexxole.dll >> rexx.dll >> rexx.exe >> rexx.img >> rexxapi.dll >> rexxutil.dll >> rxapi.exe >> rxwinsys.dll >> ooDialog.cls >> ooDialog.com >> oodialog.dll >> ooDialog.exe >> oodPlain.cls >> oodWin32.cls >> ooSQLite.cls >> oosqlite.dll >> ooSQLite3.exe >> >> Doing the same to another Win7 system without a preinstalled ooRexx works >> fine. So there seems to be some sort of incompatibility introduced between >> ooDialog and ooRexx that has been caused by the new compile. >> >> To activate the XP support in VS 2012 with SP3 I had to add the following >> before running the vcvarsall.bat: >> >> @set INCLUDE=%ProgramFiles(x86)%\Microsoft >> SDKs\Windows\7.1A\Include;%INCLUDE% >> @set PATH=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Bin;%PATH% >> @set LIB=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Lib;%LIB% >> @set CL=/D_USING_V110_SDK71_;%CL% >> @set LINK=/SUBSYSTEM:CONSOLE,5.01 %LINK% >> @"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" >> >> I suspect CL= and/or LINK= is causing this but I'm unable to say why. And >> btw, all of the above is 32-bit. >> >> A helpful hand is appreciated. >> >> Staffan >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Android is increasing in popularity, but the open development platform >> that >> developers love is also attractive to malware creators. Download this >> white >> paper to learn more about secure code signing practices that can help keep >> Android apps secure. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Oorexx-users mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-users >> >> > |
From: Staffan T. <sta...@gm...> - 2013-10-29 19:56:57
|
Mark, I tried running rexx.exe directly against a rexx program but it failed in the same way. Actually ooDialog.exe is not used by the app so it shouldn't have been on the list in the first place. Long time ago I tried to compile ooRexx on my own but got so many problems that I gave up. And I haven't tried since. But maybe it's time for a new attempt. I will have a go but may need guidelines on the way as I've understood it's a different beast than the rest. Staffan On Tue, Oct 29, 2013 at 7:18 PM, Mark Miesfeld <mie...@gm...> wrote: > Staffan, > > You most likely need to build ooRexx with the same procedure as you built > ooDialog and ooSQLite to have a chance for it to work. > > Who knows what: @set CL=/D_USING_V110_SDK71_;%CL% > > causes the compiler and linker to do. Using the ooRexx binaries built by > an older compiler version, on the face of it, seems likely to fail. > > -- > Mark Miesfeld > > > > > On Tue, Oct 29, 2013 at 11:10 AM, Mark Miesfeld <mie...@gm...>wrote: > >> It's hard to say Staffan. >> >> What happens if you leave ooDialog.exe out of the picture? Just run an >> ooDialog program through rexx.exe. For example, go to the the examples >> directory and: >> >> rexx.exe animalGame.rex >> >> -- >> Mark Miesfed >> >> >> On Tue, Oct 29, 2013 at 10:48 AM, Staffan Tylen <sta...@gm...>wrote: >> >>> After a lot of research (and swearing) I've managed to compile ooDialog >>> and ooSQLite using VS 2012 with SP3 installed to support XP as target >>> system. The compiles run with no apparent problems. And the resulting load >>> modules run as expected on my Win7 system. But when I try it all on my >>> older XP system it fails with the following: >>> >>> AppName ooDialog.exe >>> AppVer: 4.2.4.9490 >>> ModName: rexxapi.dll >>> ModVer: 4.1.3.9341 >>> Offset: 00001efa >>> >>> ooRexx is not preinstalled on my XP system so I carry over all of the >>> following from the Win7 system to the XP system together with my app: >>> >>> orexxole.dll >>> rexx.dll >>> rexx.exe >>> rexx.img >>> rexxapi.dll >>> rexxutil.dll >>> rxapi.exe >>> rxwinsys.dll >>> ooDialog.cls >>> ooDialog.com >>> oodialog.dll >>> ooDialog.exe >>> oodPlain.cls >>> oodWin32.cls >>> ooSQLite.cls >>> oosqlite.dll >>> ooSQLite3.exe >>> >>> Doing the same to another Win7 system without a preinstalled ooRexx >>> works fine. So there seems to be some sort of incompatibility introduced >>> between ooDialog and ooRexx that has been caused by the new compile. >>> >>> To activate the XP support in VS 2012 with SP3 I had to add the >>> following before running the vcvarsall.bat: >>> >>> @set INCLUDE=%ProgramFiles(x86)%\Microsoft >>> SDKs\Windows\7.1A\Include;%INCLUDE% >>> @set PATH=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Bin;%PATH% >>> @set LIB=%ProgramFiles(x86)%\Microsoft SDKs\Windows\7.1A\Lib;%LIB% >>> @set CL=/D_USING_V110_SDK71_;%CL% >>> @set LINK=/SUBSYSTEM:CONSOLE,5.01 %LINK% >>> @"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat" >>> >>> I suspect CL= and/or LINK= is causing this but I'm unable to say why. >>> And btw, all of the above is 32-bit. >>> >>> A helpful hand is appreciated. >>> >>> Staffan >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Android is increasing in popularity, but the open development platform >>> that >>> developers love is also attractive to malware creators. Download this >>> white >>> paper to learn more about secure code signing practices that can help >>> keep >>> Android apps secure. >>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Oorexx-users mailing list >>> Oor...@li... >>> https://lists.sourceforge.net/lists/listinfo/oorexx-users >>> >>> >> > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Mark M. <mie...@gm...> - 2013-10-29 20:18:47
|
On Tue, Oct 29, 2013 at 12:56 PM, Staffan Tylen <sta...@gm...>wrote: > Mark, I tried running rexx.exe directly against a rexx program but it > failed in the same way. Actually ooDialog.exe is not used by the app so it > shouldn't have been on the list in the first place. > > Long time ago I tried to compile ooRexx on my own but got so many problems > that I gave up. And I haven't tried since. But maybe it's time for a new > attempt. I will have a go but may need guidelines on the way as I've > understood it's a different beast than the rest. > It's not really different than what you have been doing. It just uses a .bat to drive the make, rather than a traditional make file. If I were you, I would use the 4.1 fixes branch: https://svn.code.sf.net/p/oorexx/code-0/main/branches/4.1/trunk * Set up your compile environment just like you do to compile ooDialog. * Set 2 environment variables set SRC_DRV=C: set SRC_DIR=\work.ooRexx\wc\main.4.1.fixes SRC_DRV is the drive letter. SRC_DIR is the top-level directory of the source code tree. * Populate the doc directory with the docs or fake files. You only need to do this if you want to try and create the installer package. You could just skip it and take the built binaries and use them Then cd to the top level directory of your ooRexx source code tree and run: makeorx NODEBUG The windows-build.txt file is reasonably up to date. I'd read that for details and then ask questions if you need to. -- Mark Miesfeld |
From: Staffan T. <sta...@gm...> - 2013-10-30 15:25:36
|
> The windows-build.txt file is reasonably up to date. I'd read that for > details and then ask questions if you need to. > > Thanks for the tips, Mark. After a lot of fiddling I've managed to get as far as compiling the rexxapi and the interpreter, but then it fails with the follow in OREXXOLE: Compiling events.cpp cl /EHsc /nologo /D:_X86_ /DWIN32 -DORX_VER=4 -DORX_REL=1 -DORX_MOD=4 -DOOREXX_BLD=9491 -DOOREXX_COPY_YEAR=\""2005-2013"\" /W3 /D_CRT_SECURE_NO_DEPRECATE /D_CRT_NONSTDC_NO_DEPRECATE -c -O2 /Gr /DNDEBUG /Gs /FAcs /FaC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\Win32Rel\ASM\events.asm /DNULL=0 /MT /FoC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\Win32Rel\events.obj -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\lib\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\common\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\common\platform\windows\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\api\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\api\platform\windows\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\classes\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\classes\support\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\runtime\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\behaviour\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\concurrency\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\execution\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\memory\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\package\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\expression\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\instructions\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\parser\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\platform\windows\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\streamLibrary\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\messages\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\platform\windows\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\rexutils\windows -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\platform\windows\oodialog\ -I\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\platform\windows\ole\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\platform\windows\orxscrpt\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\interpreter\messages\ -IC:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\hostemu\ C:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\platform\windows\ole\events.cpp events.cpp C:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\platform\windows\ole\events.cpp(51) : fatal error C1083: Cannot open include file: 'agtctl_i.c': No such file or directory NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2' Stop. I've found the missing agtctl_i.c in a MinGW folder so have tried to add the following to compile.bat but it doesn't help: set LIB=C:\MinGW64\x86_64-w64-mingw32\libsrc;%LIB% set LIBPATH=C:\MinGW64\x86_64-w64-mingw32\libsrc;%LIBPATH% How can I solve this please? Staffan |
From: Mark M. <mie...@gm...> - 2013-10-30 15:54:21
|
Hi Staffan, On Wed, Oct 30, 2013 at 8:25 AM, Staffan Tylen <sta...@gm...>wrote: > Thanks for the tips, Mark. After a lot of fiddling I've managed to get as > far as compiling the rexxapi and the interpreter, but then it fails with > the follow in OREXXOLE: > > ... > C:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\extensions\platform\windows\ole\events.cpp(51) > : fatal error C1083: Cannot open include file: 'agtctl_i.c': No such file > or directory > NMAKE : fatal error U1077: '"C:\Program Files (x86)\Microsoft Visual > Studio 11.0\VC\BIN\cl.EXE"' : return code '0x2' > Stop. > > I've found the missing agtctl_i.c in a MinGW folder so have tried to add > the following to compile.bat but it doesn't help: > The directory containing agtctl_i.c has to be in the include path, not the lib path. But, you are doing this all wrong if you are trying to compile using any MinGW files. This finally explains to me all the weird errors you are always getting when you try to compile. You need to compile using a Microsoft Visual C++ compiler and a Microsoft Windows SDK. Both of which are free if you use the express version of the compiler. We don't support MinGW. You need to set up a build environment that is using only the VC++ and MS Windows SDK files. If anything points to MinGW files you are likely to have problems. On my system agtctl_i.c is in the include directory of the 7.1 SDK: Directory of C:\Tools\Microsoft.SDKs\v7.1\Include 04/19/2010 08:43 PM 3,835 AgtCtl_i.c If your compile doesn't find it, then your build environment is not set up correctly. -- Mark Miesfeld |
From: Staffan T. <sta...@gm...> - 2013-10-30 16:12:43
|
> The directory containing agtctl_i.c has to be in the include path, not the > lib path. > > Aaah, silly me! > But, you are doing this all wrong if you are trying to compile using any > MinGW files. This finally explains to me all the weird errors you are > always getting when you try to compile. > > You need to compile using a Microsoft Visual C++ compiler and a Microsoft > Windows SDK. Both of which are free if you use the express version of the > compiler. We don't support MinGW. > > You need to set up a build environment that is using only the VC++ and MS > Windows SDK files. If anything points to MinGW files you are likely to > have problems. > > On my system agtctl_i.c is in the include directory of the 7.1 SDK: > > Directory of C:\Tools\Microsoft.SDKs\v7.1\Include > > No worry, for historical reasons I have my folder structure under MinGW but I use Windows C++ for compile. Just haven't been bothered to change it. I found the missing module also in C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include and after doing a SET INCLUDE it all seems to work OK. Here is the output: Building Rexxapi.. Building Interpreter.... Building OREXXOLE.. Building Rexxutil.. Building rexximage command launcher Building rexx command launcher Building rexxhide command launcher Building rexxpaws command launcher Building rexxc command launcher Building REXX.IMG ... Building RXSUBCOM and RXQUEUE.. Building rxwinsys.dll Building RxSock.. Building RxMath.. Building RXREGEXP... Building HOSTEMU.. Building miscellaneous extensions Building OODIALOG.. Building OODIALOG classes Building API Samples.. Include path is C:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\Win32Rel;C:\MinGW64\msys\home\Staffan\ooRexx\ooRexx.4.1\api;C:\MinGW64\msys\home\Staffa n\ooRexx\ooRexx.4.1\api\platform\windows;C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include;C:\Program Files (x86)\Microsoft Visual Studio 11 .0\VC\INCLUDE;C:\Program Files (x86)\Windows Kits\8.0\include\shared;C:\Program Files (x86)\Windows Kits\8.0\include\um;C:\Program Files (x86)\Windows Kits\8.0\include\winrt;C:\Program Files (x86)\Microsoft SDKs\Windows\7.1A\Include; Building OODialog Samples.. No error messages so I guess it should be OK. I now need to determine if this has solved my XP issues. Watch this space! Staffan |
From: Chip D. <ch...@av...> - 2013-10-30 18:13:35
|
On 10/30/2013 12:12 Staffan Tylen said: > > The directory containing agtctl_i.c has to be in the include path, > not the lib path. > > Aaah, silly me! > > No error messages so I guess it should be OK. ... <spits coffee> BWAH-hah-hah-haaa... <SNORT> If I had a penny for every time I've said that! :-)) -Chip- |
From: Staffan T. <sta...@gm...> - 2013-10-30 17:44:53
|
<?xml version="1.0" encoding="UTF-16"?> <DATABASE> <EXE NAME="ooDialog.exe" FILTER="GRABMI_FILTER_PRIVACY"> <MATCHING_FILE NAME="oodialog.dll" SIZE="640512" CHECKSUM="0xBB2E8890" BIN_FILE_VERSION="4.2.4.9490" BIN_PRODUCT_VERSION="4.2.4.9490" PRODUCT_VERSION="4.2.4.9490" FILE_DESCRIPTION="ooDialog an Open Object Rexx extension" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.2.4.9490" ORIGINAL_FILENAME="oodialog.dll" INTERNAL_NAME="ooDialog" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.2.4.9490" UPTO_BIN_PRODUCT_VERSION="4.2.4.9490" LINK_DATE="10/30/2013 17:17:38" UPTO_LINK_DATE="10/30/2013 17:17:38" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="ooDialog.exe" SIZE="287232" CHECKSUM="0x85684D9" BIN_FILE_VERSION="4.2.4.9490" BIN_PRODUCT_VERSION="4.2.4.9490" PRODUCT_VERSION="4.2.4.9490" FILE_DESCRIPTION="ooDialog Program Launcher" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="ooDialog, a Windows Extension to Open Object Rexx" FILE_VERSION="4.2.4.9490" ORIGINAL_FILENAME="ooDialog.exe" INTERNAL_NAME="ooDialog" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.2.4.9490" UPTO_BIN_PRODUCT_VERSION="4.2.4.9490" LINK_DATE="10/30/2013 17:17:39" UPTO_LINK_DATE="10/30/2013 17:17:39" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="oosqlite.dll" SIZE="1923072" CHECKSUM="0x9951859B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/30/2013 17:20:33" UPTO_LINK_DATE="10/30/2013 17:20:33" /> <MATCHING_FILE NAME="ooSQLite3.exe" SIZE="1828352" CHECKSUM="0x18487B8" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" LINK_DATE="10/30/2013 17:20:34" UPTO_LINK_DATE="10/30/2013 17:20:34" /> <MATCHING_FILE NAME="orexxole.dll" SIZE="134656" CHECKSUM="0x3D5BD9EC" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Component" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:06:11" UPTO_LINK_DATE="10/30/2013 16:06:11" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="rexx.dll" SIZE="857600" CHECKSUM="0x4CE043E5" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Interpreter (main)" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="REXX.DLL" INTERNAL_NAME="REXX" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:06:09" UPTO_LINK_DATE="10/30/2013 16:06:09" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="rexx.exe" SIZE="66048" CHECKSUM="0xC8E2262E" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Interface" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="REXX.EXE" INTERNAL_NAME="Rexx console" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:06:14" UPTO_LINK_DATE="10/30/2013 16:06:14" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="rexxapi.dll" SIZE="145920" CHECKSUM="0x5EF3C6B5" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Component" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:04:23" UPTO_LINK_DATE="10/30/2013 16:04:23" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="rexxutil.dll" SIZE="263680" CHECKSUM="0xDBA25971" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Component" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:06:12" UPTO_LINK_DATE="10/30/2013 16:06:12" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="rxapi.exe" SIZE="117248" CHECKSUM="0xCE2C1545" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx API manager" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="RXAPI.EXE" INTERNAL_NAME="API manager" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x1" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:04:27" UPTO_LINK_DATE="10/30/2013 16:04:27" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> <MATCHING_FILE NAME="rxwinsys.dll" SIZE="120320" CHECKSUM="0xA12114BF" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Component" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:06:19" UPTO_LINK_DATE="10/30/2013 16:06:19" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> </EXE> <EXE NAME="REXXAPI.dll" FILTER="GRABMI_FILTER_THISFILEONLY"> <MATCHING_FILE NAME="rexxapi.dll" SIZE="145920" CHECKSUM="0x5EF3C6B5" BIN_FILE_VERSION="4.1.4.9491" BIN_PRODUCT_VERSION="4.1.4.9491" PRODUCT_VERSION="4.1.4.9491" FILE_DESCRIPTION="Open Object Rexx Component" COMPANY_NAME="Rexx Language Association" PRODUCT_NAME="Open Object Rexx for Windows" FILE_VERSION="4.1.4.9491" ORIGINAL_FILENAME="" INTERNAL_NAME="" LEGAL_COPYRIGHT="Copyright © RexxLA 2005-2013." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x0" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="4.1.4.9491" UPTO_BIN_PRODUCT_VERSION="4.1.4.9491" LINK_DATE="10/30/2013 16:04:23" UPTO_LINK_DATE="10/30/2013 16:04:23" VER_LANGUAGE="Inglés (Estados Unidos) [0x409]" /> </EXE> <EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY"> <MATCHING_FILE NAME="kernel32.dll" SIZE="1043456" CHECKSUM="0x3A603BA0" BIN_FILE_VERSION="5.1.2600.6293" BIN_PRODUCT_VERSION="5.1.2600.6293" PRODUCT_VERSION="5.1.2600.6293" FILE_DESCRIPTION="DLL de cliente API BASE de Windows NT" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Sistema operativo Microsoft® Windows®" FILE_VERSION="5.1.2600.6293 (xpsp_sp3_gdr.121001-1622)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="Copyright (C) Microsoft Corporation. Reservados todos los derechos." VERFILEDATEHI="0x0" VERFILEDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xFF574" LINKER_VERSION="0x50001" UPTO_BIN_FILE_VERSION="5.1.2600.6293" UPTO_BIN_PRODUCT_VERSION="5.1.2600.6293" LINK_DATE="10/03/2012 04:58:02" UPTO_LINK_DATE="10/03/2012 04:58:02" VER_LANGUAGE="Español (alfabetización internacional) [0xc0a]" /> </EXE> </DATABASE> |
From: Mark M. <mie...@gm...> - 2013-10-30 17:55:02
|
Take ooDialog.exe and ooDialog.com and put them in a temp directory not in the path. Doubt that will change anything, but ooDialog.exe should not be in the listing if it is not loaded and there is no reason for it to be loaded. -- Mark Miesfeled On Wed, Oct 30, 2013 at 10:44 AM, Staffan Tylen <sta...@gm...>wrote: > > No error messages so I guess it should be OK. I now need to determine if >> this has solved my XP issues. Watch this space! >> >> > Bad news, I still get the error but with a different offset: > > AppName: oodialog.exe > AppVer: 4.2.4.9490 > ModName: rexxapi.dll > ModVer: 4.1.4.9491 > Offset: 000020f1 > > I attach an xml file that was generated by the system at the time of the > error if anybody wants to have a look. This is beyond me ... > > Staffan > > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Art H. <art...@ar...> - 2013-10-30 21:21:43
|
<html><head><meta name="Generator" content="PSI HTML/CSS Generator"/> <style type="text/css"><!-- body{font-family:'Tahoma';font-size:12pt;font-color:'#000000';} LI{display:list-item;margin:0.00in;} p{display:block;margin:0.00in;} body{} --></style> </head><BODY ><div><SPAN style="font-size:12pt;color:navy;">How would I go about having something like a Listbox with a header</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">area?  I am wanting the "header" portion to stay visible when the box</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">is vertically scrolled, and to move right/left when the box is scrolled</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">horizontally.  Optionally, I would also like for the "header" to be </SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">either in a font different from the rest of the box, or maybe just</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">underlined.  Would I use a ListView with a ListBox as a Grandchild</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">Parent setup, using the ListBox for the "header" area?  Suggestions,</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">but you need not develop a new example for this right now :-)</SPAN><SPAN style="font-size:12pt;"><br /><br />--<br />  Art Heimsoth - art...@ar...</SPAN></div> </body></html> |
From: Mark M. <mie...@gm...> - 2013-10-30 21:44:16
|
On Wed, Oct 30, 2013 at 2:21 PM, Art Heimsoth <art...@ar...>wrote: > How would I go about having something like a Listbox with a header > area? I am wanting the "header" portion to stay visible when the box > is vertically scrolled, and to move right/left when the box is scrolled > horizontally. > Art, I don't really think this is possible with a list box, in ooDialog. There is a Header control that ooDialog doesn't support yet. (I plan to in the future.) The Header control is what a list view uses for the header. It creates the control with itself as the owner, which is what keeps the header within the client area of the list view. The header control then sends its notification messages to the list view and the list view handles them. When the Header control is added, I still think this would be difficult. We would have to work out the details, but it might be doable. -- Mark Miesfeld |
From: Art H. <art...@ar...> - 2013-10-31 00:45:16
|
<html><head><meta name="Generator" content="PSI HTML/CSS Generator"/> <style type="text/css"><!-- body{font-family:'Tahoma';font-size:12pt;font-color:'#000000';} LI{display:list-item;margin:0.00in;} p{display:block;margin:0.00in;} body{} --></style> </head><BODY ><div><SPAN style="font-size:12pt;color:navy;">> On Wed, Oct 30, 2013 at 2:21 PM, Art Heimsoth</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> <art...@ar...> wrote:</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:maroon;">>> How would I go about having something like a Listbox with a header</SPAN></div> <div><SPAN style="font-size:12pt;color:maroon;">>></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> area?  I am wanting the "header" portion to stay visible when the</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> box is vertically scrolled, and to move right/left when the box is</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> scrolled horizontally.  </SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> Art, I don't really think this is possible with a list box, in</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> ooDialog.  There is a Header control that ooDialog doesn't support</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> yet.  (I plan to in the future.)</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> The Header control is what a list view uses for the header.  It</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> creates the control with itself as the owner, which is what keeps</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> the header within the client area of the list view.  The header</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> control then sends its notification messages to the list view and</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> the list view handles them.</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> When the Header control is added, I still think this would be</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> difficult.  We would have to work out the details, but it might be</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> doable.</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">></SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> --</SPAN></div> <div><SPAN style="font-size:12pt;color:navy;">> Mark Miesfeld</SPAN><SPAN style="font-size:12pt;"><br /><br />Gee Mark, I think this is the first time you couldn't come through for</SPAN></div> <div><SPAN style="font-size:12pt;">me !!  Thanks anyway - what I have works (for now...).</SPAN></div> <div><SPAN style="font-size:12pt;"><br />--<br />  Art Heimsoth - art...@ar...</SPAN></div> </body></html> |
From: Staffan T. <sta...@gm...> - 2013-10-31 09:46:21
|
Art, I had a similar wish but only to find out (via Mark's usual help) that it is not possible (at least not for the moment). So what I did was to defined a frame, where I used the upper part of the frame as header area and the lower part for the list view. The result looks similar to a list view with headers but the limitation is that you can't scroll sideways, change the column order, or resize the columns. But with some fiddling I managed to get the header area to resize correctly in a resizeable window, and this fulfilled my requirement. Staffan On Thu, Oct 31, 2013 at 1:45 AM, Art Heimsoth <art...@ar...>wrote: > > On Wed, Oct 30, 2013 at 2:21 PM, Art Heimsoth > > <art...@ar...> wrote: > > > >> How would I go about having something like a Listbox with a header > >> > > area? I am wanting the "header" portion to stay visible when the > > box is vertically scrolled, and to move right/left when the box is > > scrolled horizontally. > > > > > > Art, I don't really think this is possible with a list box, in > > ooDialog. There is a Header control that ooDialog doesn't support > > yet. (I plan to in the future.) > > > > > > The Header control is what a list view uses for the header. It > > creates the control with itself as the owner, which is what keeps > > the header within the client area of the list view. The header > > control then sends its notification messages to the list view and > > the list view handles them. > > > > > > When the Header control is added, I still think this would be > > difficult. We would have to work out the details, but it might be > > doable. > > > > > > -- > > Mark Miesfeld > > Gee Mark, I think this is the first time you couldn't come through for > me !! Thanks anyway - what I have works (for now...). > > -- > Art Heimsoth - art...@ar... > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |
From: Mark M. <mie...@gm...> - 2013-10-31 13:40:42
|
I have one other comment on this subject. Why not just use a list view? Even if ooDialog did have support for the Header control, there is really a lot of work to manage the Header. The list view does all that work for you. Another drawback is that if you did use a Header control with a list box, the list box doesn't know about the header so the header would obscure some rows in the list box. The solution to that is to make the list box owner drawn. Owner draw is something you can do in C / C++ code, but it is also a lot of work. Being able to do it from ooDialog is problematic in my mind. And, again, all the work is done for you in a list view. -- Mark Miesfeld On Thu, Oct 31, 2013 at 2:45 AM, Staffan Tylen <sta...@gm...>wrote: > Art, I had a similar wish but only to find out (via Mark's usual help) > that it is not possible (at least not for the moment). So what I did was to > defined a frame, where I used the upper part of the frame as header area > and the lower part for the list view. The result looks similar to a list > view with headers but the limitation is that you can't scroll sideways, > change the column order, or resize the columns. But with some fiddling I > managed to get the header area to resize correctly in a resizeable window, > and this fulfilled my requirement. > > Staffan > > > > On Thu, Oct 31, 2013 at 1:45 AM, Art Heimsoth <art...@ar...>wrote: > >> > On Wed, Oct 30, 2013 at 2:21 PM, Art Heimsoth >> > <art...@ar...> wrote: >> > >> >> How would I go about having something like a Listbox with a header >> >> >> > area? I am wanting the "header" portion to stay visible when the >> > box is vertically scrolled, and to move right/left when the box is >> > scrolled horizontally. >> > >> > >> > Art, I don't really think this is possible with a list box, in >> > ooDialog. There is a Header control that ooDialog doesn't support >> > yet. (I plan to in the future.) >> > >> > >> > The Header control is what a list view uses for the header. It >> > creates the control with itself as the owner, which is what keeps >> > the header within the client area of the list view. The header >> > control then sends its notification messages to the list view and >> > the list view handles them. >> > >> > >> > When the Header control is added, I still think this would be >> > difficult. We would have to work out the details, but it might be >> > doable. >> > >> > >> > -- >> > Mark Miesfeld >> >> Gee Mark, I think this is the first time you couldn't come through for >> me !! Thanks anyway - what I have works (for now...). >> >> -- >> Art Heimsoth - art...@ar... >> >> >> ------------------------------------------------------------------------------ >> Android is increasing in popularity, but the open development platform >> that >> developers love is also attractive to malware creators. Download this >> white >> paper to learn more about secure code signing practices that can help keep >> Android apps secure. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk >> _______________________________________________ >> Oorexx-users mailing list >> Oor...@li... >> https://lists.sourceforge.net/lists/listinfo/oorexx-users >> >> > > > ------------------------------------------------------------------------------ > Android is increasing in popularity, but the open development platform that > developers love is also attractive to malware creators. Download this white > paper to learn more about secure code signing practices that can help keep > Android apps secure. > http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk > _______________________________________________ > Oorexx-users mailing list > Oor...@li... > https://lists.sourceforge.net/lists/listinfo/oorexx-users > > |