Welcome, Guest. Please login or register.

Login with username, password and session length

 
Advanced search

11991 Posts in 1587 Topics- by 3508 Members - Latest Member: NevilleKemp

26. May 2012, 06:19:44 pm
Xith3D CommunityGeneral CategorySupport (Moderator: Marvin Fröhlich)Link issues
Pages: [1]
Print
Author Topic: Link issues  (Read 980 times)
horati
Global Moderator
Getting respectable
*****
Offline Offline

Posts: 393


View Profile
« on: 19. February 2007, 01:50:16 pm »

Marvin, thanks for the display bounds fix yesterday.  Now, my shared objects no longer disappear.

I deleted my earlier post about picking problems with links.  My problem was that I was using Canvas3D.pick() instead of PickingLibrary.  Now I am using PickingLibrary and it picks.  Yay!!  However, the bounds for the Link do not match the underlying bounds; i.e., I can only pick my cubes if I click within about 2 pixels of the upper left corner.
Logged

Kevin
"It may not seem like a big deal, but ignorance of character encoding issues leads to insidious code rot akin to y2k."
http://stackoverflow.com/users/3474/sylvarking
Marvin Fröhlich
Xith Lord
Administrator
Guru
*****
Offline Offline

Posts: 4381


May the 4th, be with you...


View Profile
« Reply #1 on: 19. February 2007, 03:21:38 pm »

Marvin, thanks for the display bounds fix yesterday.  Now, my shared objects no longer disappear.

Cool.

However, the bounds for the Link do not match the underlying bounds; i.e., I can only pick my cubes if I click within about 2 pixels of the upper left corner.

Yeah, Canvas3D.pick*() will never be able to pick on Links.And it is much slower than PickingLibrary (and PickScheduler). But I have quite exact plans, what to do to improve speed.

However, the bounds for the Link do not match the underlying bounds; i.e., I can only pick my cubes if I click within about 2 pixels of the upper left corner.

Thanks for the hint. I will check it.

Marvin
Logged
Marvin Fröhlich
Xith Lord
Administrator
Guru
*****
Offline Offline

Posts: 4381


May the 4th, be with you...


View Profile
« Reply #2 on: 19. February 2007, 06:38:13 pm »

I had another look at the bounds code. But I can'T seem to find, why the link bounds are too small. Though I handled the link bounds a bit differently now. Please try, if that fixed it.

Marvin
Logged
horati
Global Moderator
Getting respectable
*****
Offline Offline

Posts: 393


View Profile
« Reply #3 on: 19. February 2007, 09:31:36 pm »

Sorry for taking so long to get back.  My computer locked up during the middle of a compile.  It corrupted a bunch of my files and my file system so I had to restore from SVN and get everything working again.

Nope, this didn't change a thing.
Logged

Kevin
"It may not seem like a big deal, but ignorance of character encoding issues leads to insidious code rot akin to y2k."
http://stackoverflow.com/users/3474/sylvarking
Marvin Fröhlich
Xith Lord
Administrator
Guru
*****
Offline Offline

Posts: 4381


May the 4th, be with you...


View Profile
« Reply #4 on: 19. February 2007, 09:40:55 pm »

Nope, this didn't change a thing.

Really strange. Now we are at the point, where I need some test coding, since I cannot reproduce this bug. Please send me something.

Marvin
Logged
horati
Global Moderator
Getting respectable
*****
Offline Offline

Posts: 393


View Profile
« Reply #5 on: 20. February 2007, 11:35:08 am »

Thanks for staying so long last night Marvin.  I grabbed a bite to eat and came back to the computer about 10 minutes after you left.  Indeed, your fixes corrected the FOV.  I tried it through view.setFOV() and rp.setFOV() and both worked.  My code now uses rp.setFOV() and pick scheduling.

Thanks again!!   Grin
Logged

Kevin
"It may not seem like a big deal, but ignorance of character encoding issues leads to insidious code rot akin to y2k."
http://stackoverflow.com/users/3474/sylvarking
Marvin Fröhlich
Xith Lord
Administrator
Guru
*****
Offline Offline

Posts: 4381


May the 4th, be with you...


View Profile
« Reply #6 on: 20. February 2007, 06:36:03 pm »

Thanks for staying so long last night Marvin.  I grabbed a bite to eat and came back to the computer about 10 minutes after you left.  Indeed, your fixes corrected the FOV.  I tried it through view.setFOV() and rp.setFOV() and both worked.  My code now uses rp.setFOV() and pick scheduling.

Thanks again!!   Grin

You're welcome. I'm glad to see everything working for you now Smiley.

Marvin
Logged
Pages: [1]
Print
Jump to:  

Theme orange-lt created by panic