Updating fluff, flit, and flpicsee updates to fltk-1.4

[MikeLockmoore]

Looking good, a few comments:

Maybe the configuration files would be better saved in ~/.config/name (i.e. ~/.config/flit/flit.conf) rather than ~/?

If there is no sound enabled (the default for me) saving the flit config results in a seg fault and an empty conf file

If I open a large image in flpicsee it selects 25% zoom, but the title bar is off the screen with 1366x768 using flwm classic and I need to use <ctrl-m> x2 to get it back.

Thanks for your feedback!  I agree the ~/.config location would be better housekeeping.  I can move to that for both Fluff and Flit.

I'll try to troubleshoot your 'no sound' configuration crash.

Are you saying that a really big image is just going with 25% zoom in FlPicsee, even if that is not zoomed out enough to keep the full frame on-screen?  What happens if you use the right-click menu and select "nice" or whole-image, or fill zoom levels? How big is the original image?

I'll try to investigate your issues and work on your suggestions in coming days.

[MikeLockmoore]

In the latest fluff, there's an issue with not resetting the file list display when using the back button.  ...
I think when the back button is clicked it should either re-select the previously selected file in the target directory or should reset the file list display to the to the first file in the list (as determined by the sort order).

Leee, I've implemented the "reset the file list display to the first file in the list" approach and it seems to work.  However, I noticed during testing that some filess have properties that are difficult to access, leading to 'stat64( )' warnings on the console if you start Fluff from the command-line, and even worse, Fluff will crash if displaying the File Properties dialog box for one of these bad files and then click the "Info" button.  I need to investigate that and develop a more robust way of handling that situation. 

[Leee]

In the latest fluff, there's an issue with not resetting the file list display when using the back button.  ...
I think when the back button is clicked it should either re-select the previously selected file in the target directory or should reset the file list display to the to the first file in the list (as determined by the sort order).

Leee, I've implemented the "reset the file list display to the first file in the list" approach and it seems to work.  However, I noticed during testing that some filess have properties that are difficult to access, leading to 'stat64( )' warnings on the console if you start Fluff from the command-line, and even worse, Fluff will crash if displaying the File Properties dialog box for one of these bad files and then click the "Info" button.  I need to investigate that and develop a more robust way of handling that situation.

I tried looking at properties on a few files in my home directory but the Info button wasn't enabled for any of them.
Eventually, I selected a symlink ( /etc/sysconfig/tcedir ) and the Info button was enabled on the properties dialog.
Clicking the Info button did not crash fluff (and no messages had been generated on the console) but the only visible action was that, in the file list, fluff navigated to the tce directory as if I had double clicked on the symlink.  Is this the expected behavior,

[MikeLockmoore]

I tried looking at properties on a few files in my home directory but the Info button wasn't enabled for any of them.
Eventually, I selected a symlink ( /etc/sysconfig/tcedir ) and the Info button was enabled on the properties dialog.
Clicking the Info button did not crash fluff (and no messages had been generated on the console) but the only visible action was that, in the file list, fluff navigated to the tce directory as if I had double clicked on the symlink.  Is this the expected behavior,

The files I was having trouble with were things like /proc/16/cwd and /proc/16/root.  The libc function stat64() to look up file properties like file ownership and access permissions can sometimes fail, so in recent versions of Fluff you can see "stat64(): permission denied" messages or similar on the command-line, and you get blank line in the file details window besides the file name for the affected particular files.  But apparently these files are links to other directories, so the info button gets enabled.  I'm not sure what I intended at this point with the info button... but jumping to the linked folder seems weird and probably not what I intended before.  I'll look at this in more detail in the next day or so.  I may remove the button or rename it.  Thanks again for testing and providing feedback!
- Mike