![]() ![]() Writing a file can take a surprisingly long time - especially when you consider that writing a file isn't necessarily just "writing" a file. So if feh is reloading the same image every 10 seconds, for example, you might expect to see some amount of gray about 1% to 10% of the time. I of course have no clue what kind of "export script" you're using to generate the JPG file, but it could easily take a good chunk of a full second to complete the write. In the "few times" you saw an incomplete image, feh was almost certainly catching the image "in the act" of being written to the storage device by your script!įor example, if feh happens to reload the image at the exact moment only 70% of the JPG file has been written, then the top 70% of the image would appear normal and the bottom 30% would be gray (indicating "no data").įeh is doing its job perfectly - it's showing you EXACTLY what the contents of the image file look like at that exact moment! Let me start by saying that no image viewer in the world can fully display an image that does not fully exist! To understand the full context, please start here. ![]() The image display is controlled by my fehshow command. The image file is continuously overwritten at regular intervals and displayed on a large screen to show employees the live status of items at a warehouse. NOTE TO OTHER READERS: This person is using a script to export the contents of a FileMaker database to a JPG image. This may not be a question you can answer but here goes.Ī few times the bottom half of the display changes to all gray. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |