WinLib Bugs 12/2007
- Posted by Al Getz <Xaxo at a?l.?om> Dec 14, 2007
- 506 views
Hello there, I DL'd the latest version (i guess it is) from the archives and ran into a few problems. I'll number them here... 1. Trying to unzip the .zip file leads to a problem (XP-SP2) that says that some of the files are password protected. This makes it harder to unzip and therefore use the library. This should be corrected. 2. In file w32resources.ew, in procedure setPrinterPointers, apparently this function is called automatically as the lib is loaded. The problem comes in when the user does not have a printer installed in the system (had problems with mine so im not using it right now). The vDevmodeSize variable gets loaded to -1 and this causes an error 473 that states that memory can not be allocated. The workaround was to simply test this var for less than zero and load it with 256. This number was picked at random just to get things booted up so more research time will have to be put into this issue for whoever is working on this Lib now. Keep in mind that many systems will not have a printer installed so it's a good idea to fix this. 3. In file version.e, in function getEuVersion(), the var s1 must be made to be an object because getenv() sometimes returns an atom. More appropriate testing on this var also has to be done to find out if it's an atom before the length can be tested, as usual. The workaround is "if atom(s1) or (not length(s1)) then" but there is more code after that too that needs to be tested for atom type. This should be easy to fix. Take care, Al E boa sorte com sua programacao Euphoria! My bumper sticker: "I brake for LED's" From "Black Knight": "I can live with losing the good fight, but i can not live without fighting it". "Well on second thought, maybe not."