I have an application that requires the display (BITMAP BUTTON) of longfilename.PCX images.

As OI does not support longfilenames I was wondering if there was any routine around that could return the dos path for a given longpathfilename.

Also, I will need to print the image with a report (Price lists). As I can only print .bmp images in OIPI, I was wondering if there was anyway of using reporter and passing the path when printing.

Any alternative solutions would be appreciated.

Barry

Hi Barry,

As OI does not support longfilenames I was wondering if there was any routine around that could return the dos path for a given longpathfilename.

What platform is your app running on?

If it's NT 4.0 I believe Krnl386.exe ( 16-bit ) exports the GetShortPathName() name API function which you can prototype in DLL_KERNEL and access direct from OI.

If it's Win 95/98 then I believe you need to thunk upto Kernel32 to get at the GetShortPathName() function, which is a bit more work ( though it can be done! )

Also, I will need to print the image with a report (Price lists). As I can only print .bmp images in OIPI, I was wondering if there was anyway of using reporter and passing the path when printing.

I don't know about Reporter, but if you're willing to do a bit of work and get yourself a copy of DataTech's ImageMan v5 DLL toolkit you could manipulate the PCX and save it to a BMP format instead ( crude, but a little less work that manuplating the file format's yourself )

Regards

[email protected]

Sprezzatura Group

World Leaders in all things RevSoft

The Server is NT , Workstations are 98…

Is that classed as 98 for the excercise

]]thunk upto Kernel32 to get at the GetShortPathName() function, which is a bit more work ( though it can be done! )

]]copy of DataTech's ImageMan v5 DLL toolkit you could manipulate the PCX and save it to a BMP format instead «

Do you mean it contains a DLL you can call, or you have to develop your own dlls using the kit…Have you used this and already have protyped DLLs available to sell.

Barry

Hi Barry,

The Server is NT , Workstations are 98…Is that classed as 98 for the excercise

Yep..

Do I Hear any bids on cost

Already done. Contact AMcA for details..it's all in a utility DLL ( called Utility32 surprisingly that exports some Win32 functionality so we can get at it via OI.

Do you mean it contains a DLL you can call, or you have to develop your own dlls using the kit…Have you used this and already have protyped DLLs available to sell.

The functions you need are all in the ImageMan DLLs that are supplied with OI ( ImageMan v5 ) so you don't really need to write your own.

However, OI is not supplied with the export libraries needed to convert and write files out ( don't know why…Licensing or just never got around to it I guess - ask RTI?). To use them you'd need the documentation too…

We've just done something similar for a client, but they purchased their own copy of Imageman so we had access to everything necessary to do the work…

Regards

Carl

Barry,

1) do you infact need the full path name?

2) Are you storing the bitmap name (and path)? We maintain a separate table for documents .. Readable Name, Doc.Name and Path.

I really wish RTI would take a few minutes out of creating new companies etc and fix this problem. OI is the only product I know of that can not use use/get directory information.

[email protected] onmouseover=window.status=imagine … ;return(true)"

David Tod Sigafoos ~ SigSolutions

Cell: 503-341-2983

[email protected]

Carl,

Is this dll the completed version of the one I tested many months ago? Are there any situation where the longfile/space in name still causes problems?

tia

[email protected] onmouseover=window.status=imagine … ;return(true)"

David Tod Sigafoos ~ SigSolutions

Cell: 503-341-2983

[email protected]

Hi DSig!

Yep, it's the same DLL, - The problem with the .exe path names was the fact that they're stored in the registry incorrectly which causes some problems with Char(0)'s and truncation - I think I got around this but it's that long since I looked at it my memory fades ( I'm 30 now y'know . AFAIK it works fine if the registry string is quoted ( as it should be 0 I believe this is a known issue and is part of the MS knowledge Base )

Actually, if I remember correctly the real problem you got was the fact that WinWord wouldn't load again - something about COM Storage Space? I believe this is a 16-]32 memeory issue, but again it's had a low priority so I haven't looked into this in detail yet?

Where there any other issues you can remember? Was there anything else you wanted?

I don't know of any problems with the functionality ( GetShortPathName ) that Barry needs as this is nothing registry based.

Regards

Carl

Carl,

As usual (you must get tired of all the accolades .. yes? you are correct. The problem was that WinWord would stop launching.

I will be talking with Andrew later and see about testing it again .. if it can be broke I can do it

[email protected] onmouseover=window.status=imagine … ;return(true)"

David Tod Sigafoos ~ SigSolutions

Cell: 503-341-2983

[email protected]

Yo!

As usual (you must get tired of all the accolades .. yes?

I suppose so - it's such a burden, but we all have our crosses to bear don't we

The problem was that WinWord would stop launching.

Fixed. The problem is that 32-bit apps launched *directly* from a 16-bit process use the 16-bit address space which is much much smaller than the normal 32 bit space so it gets eaten real quick.

The ShellExecute/WinExec functions in the 16-bit stubs on Win32 really do some extra stuff to get around this so I decided to call them instead of the 32-bit ShellExecute directly!

The next problem is launching the Win32 Common Dialogs - They detect that they are in a 16-bit context and alter themselves back to the Win16 version as they rely on multi-threading which Win16 doesn't support *groan* . Still, I think I'll have this cracked soon!

I will be talking with Andrew later and see about testing it again .. if it can be broke I can do it

Please do - I really like fixing DLL's and debugging assembler code!!

Cheers

Carl

[email protected]

Sprezzatura Group

World Leaders in all things RevSoft

View this thread on the forum...