forums.silverfrost.com

Paul,

Has there been any progress on this issue?

That would be great. Is there a way I can be notified if/when a change is made to this function? I'm also willing to be a beta tester for any changes made. In the meantime I'll keep using the large ...

Paul,

I argue that it is well worth it because as it now stands I don't think the routine can be used for jpg files to retrieve a block size smaller than the whole image and/or a block that starts ...

Paul,

Agreed and understood, but shouldn't the call parameters for GET_DIB_BLOCK@ have the same meaning for both file types, and by doing an internal call to GET_DIB_SIZE@ for jpg files, wouldn't i ...

Apparently my message was too long and the program was truncated - here is the complete program in * CODE * format.

WINAPP 300000,500000
PROGRAM JPG
C
INTEGER*1 IBFFER( ...

After a good number of experiments, I have determined that (in my opinion) GET_DIB_BLOCK@ is behaving very differently when processing jpg images than when processing bmp images, and that the way it i ...

Paul,

Many thanks for your wisdom. I've been able to get things working for .jpg with the changes you suggested. Now I can see that .jpg processing is more sensitive to trying to read past the ac ...

My understanding reading the documentation for GET_DIB_SIZE@, GET_DIB_BLOCK@, and DISPLAY_DIB_BLOCK@ is that these should work identically for both .bmp and .jpg files. I have used these functions ju ...

When I use a line in my .rc resource script that reads

1 24 DEFAULT.MANIFEST

my radio buttons, check boxes, drop-down lists, etc all take on the XP-style of display, as desired. However, my i ...

I agree with your suggestion to change to a /INTL default, but I have been trying to avoid such a change for years, mostly 'cuz I'm an old-school programmer who cut my teeth programming in 64k ...

I have a source file which seems to compile fine with the latest version of FTN95 (4.9.1) when no debugging compiler directives are selected, but when I compile with /FULL_UNDEF selected the Call to S ...

Thanks for your quick response, Paul.

For now I'll make the following changes to my CLEARWIN.INS files for EDIT_CLIPBOARD_CUT@, EDIT_CLIPBOARD_COPY@ and EDIT_CLIPBOARD_PASTE@ -- on the C_EXTERN ...

It seems the potential problem is that if the .INS defines _CUT@ and _COPY@ as subroutines, but the help file shows them as functions and so someone calls them as functions, that this is opposite from ...