Custom Query (518 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (34 - 36 of 518)

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Ticket Resolution Summary Owner Reporter
#518 duplicate Double-clicking on invalid ZIP file results in incorrect error message John Small
Description

Double-clicking on an invalid ZIP file causes an error message regarding "The program UNZIP32.EXE is not found on the PATH or is not an executable file type." After closing that error message, FM/2 displays the window describing the problem with the zip file.

While ARCHIVER.BB2 does have an entry for UNZIP32.EXE, it is far below the one for Zip/Unzip (ZIP.EXE and UNZIP.exe).

I think FM/2 should, by default, use the first archiver it finds that has the right extension and right signature for the file being opened.

This problem may be related to Ticket #517.

#1 wontfix Use Innotek FT2LIB in FM2 Gregg Young
Description

Globally activate the font engine on font engine enabled systems. http://www.edm2.com/index.php/Ft2lib

What I recommend is to use DosLoadModule? and DosQueryProcAddr? to conditionally load and enable the library. This also needs a settings page entry before it can go into production along with code to disable the library when the setting is toggled off.

The enable/disable code should to be wrapped in utility function rather than being done in-line.

The enable code needs to go into InitFM3DLL() in init.c and should be similar to

If lib wanted

EnableFT2Lib()

EnableFT2Lib() will look something like

Try to load library If not loaded

complain

Else

Try to get address

If fail

complain

Else

enable remember enabled

The disable function, DisableFt2Lib(), will look something like

If enabled

Try to load library If not loaded

complain

Else

Try to get address If fail

complain

Else

disable remember disabled unload library unload library (since loaded by enable too)

For an example of how to use DosLoadModule? etc., see the code near line 1819 of misc.c.

#11 wontfix Add attribute "locked" to file attributes Gregg Young
Description

Now that the option exists to unlock files on copy, move or delete operations. I see no value in adding this

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Note: See TracQuery for help on using queries.