08:38:27 AM
3FK0IITOP
I still can't see the exact scenario but at least you have a workaround until V1.10 is released (hopefully next week):
manually copy your images into Site\Images folder
Sorry for the inconvenience
Yes, manually copying the two images into Site\Images folder fixed it - no GDI error on form instantiating.
Next I ran xxxTest.css.prg - again no error and form1_scx.htm and form1_scx.js were regenerated.
Next removed images from Site\Images and ran again xxxTest.css.prg - GDI error is back but htm/js are still refreshed.
Plamen
I wish I could see the issue, but frankly I don't
cImageWeb() doed a FullPath() ; it should correct the path even if wrong
Could you try copy the images into your Site\Images folder?
HTH,
thn
Yes.
When Form shows up in IDE, can you see the image(s)?
In fact there was a copy of aw.vcx that Microsoft had made for me without asking. In Windows 7 there is a feature (or bug) called VirtualStore (http://answers.microsoft.com/en-us/windows/forum/windows_7-security/how-to-disable-virtualstore-in-windows-7/55dce284-0dcd-46af-892e-d2b9cf5bcff6) that prevents direct access to some system folders. As ...\ab\ is part of "Program Files" it was also duplicated in VirtualStore and I was editing the copy. Not sure what was FIC using on run - original or copy aw.vcx as this is quite transparrent to user. After disabling VirtualStore I could edit the original aw.vcx bu this didn't eliminate the GDI+ error.
Tried the same on a XP machine where no VirtualStore exists - same result.
Plamen
-- thn (FoxInCloud)
