Page 1 of 1

Bug Report

PostPosted: Mon Dec 22, 2008 3:36 pm
by Just4Fun
I imagine that you already know about this, but...

"Access violation at address 006A0F1C in module "NeoBook.exe'. Read address 0000217"

To recreate this error: Rename polygon object in object list. Before finishing, click on next object in list to be renamed. Alert box. Same is true if you enter a carriage return.

:shock:

-Rachel

PostPosted: Tue Dec 23, 2008 12:21 am
by AlfB
Can reproduce this here. Seems to happen when you rename for the first time this way, and only when you do a right mouseclick on the next object in list. Nevertheless rename action takes place correctly and nothing else negative seems to happen.

Hope this helps

ALF

PostPosted: Tue Dec 23, 2008 10:35 am
by Neosoft Support
I can't reproduce this here with v5.6.2 on Vista. Are you using a different version of NeoBook or Windows?

PostPosted: Tue Dec 23, 2008 11:18 am
by Just4Fun
I am using the demo version of Neobook. I can reproduce this error every time. :wink:
-Rachel

PostPosted: Tue Dec 23, 2008 7:31 pm
by beno
Hi,

I can reproduce this bug. Take a look at:

http://www.benitoestrada.net/video/MyBugVideo.html

I am using Win XP SP2 Spanish and NeoBook 5.6.0 (English)

After making this test I decided to upgrade my NB to 5.6.2 and ... oops! now this error pops when I try to run NeoBook 5.6.2 on my PC

Image

And NeoBook does not starts anymore...

I reinstalled 5.6.0 and everything seems to run fine.

Oddities ... :wink:

Merry Christmas!

beno

PostPosted: Tue Dec 23, 2008 11:42 pm
by HPW
Can reproduce this here likw Alfb. Happens when you inplace-edit a entry and when you then do a right mouseclick on the next object in list.

neobook 5.6.2 on a vista laptop.
(Have not tried it yet on XP)

PostPosted: Wed Dec 24, 2008 9:42 am
by Wrangler
With 5.6.2, I can also reproduce it. It doesn't if you have only one polygon object. Create a second one, and the error occurs. It does however rename the object properly. Using XP Pro.

As this has turned out to be a small bug, maybe this post should be moved to another forum.