【转帖】rendering Bug In Singledoc Projec
 

rendering bug in singledoc project
rendering bug in singledoc project
hello,
the singledoc project crashes on a memory error when viewing the autocad sample watch.dwg file saved in model space. i could not send it because the file is too large. basically, it is the sample watch.dwg saved in model space as opposed to paperspace. the error occurs in both release and debug builds.
the same drawing intermittently works in odamfcapp. i am using the latest dd libraries, 1.11.01. i suspect it is a wingdi bug. in odamfcapp, i ocasionally get a "rendering input error".
thanks
i tried watch.dwg (~400k) from ac2002 samples. i switched to model space and saved it (with ac2002 to r15 and with ac2004 to r18)
i failed to reproduce the crash...
sergey slezkin
quote:
originally posted by sergey slezkin
i tried watch.dwg (~400k) from ac2002 samples. i switched to model space and saved it (with ac2002 to r15 and with ac2004 to r18)
i failed to reproduce the crash...
sergey,
the watch.dwg drawing i have is 1.1 mb. can i email it to you? if so, how do i get your email address?
thanks
i found 2 watch.dwg of 1.1m size - in r14 and in r2002 samples. which one did you used? by what acad it was saved in model space?
probably it would be better to get the file from you.
sslezkin_at_softdev.spb.ru
sergey slezkin
sergey,
the watch.dwg i tested is from the autocad 2002 samples with a 3/23/1999 file date. i opened it in acad 2002, switched to model space tab, and resaved it. i will email the file to you. thanks...
robert
i reproduced it! the effect depends on screen resolution and even with your file i got the the crash only after resizing window.
the reason is that dd1.11 incorrectly calculates extents of text with non-zero thickness. they are always (-1e+20, 1.e+20). depending on screen resolution viewing matrix after zoom extents may get scale like 1e-20. later normalization of vector having 1.e-20 length fails.
the defect (incorrect text extents) is already fixed.
sergey slezkin
sergey,
i am glad you found the problem. i will continue to look for bugs!
thanks...