Archived issue #0021986
[OCC Forum] MoveTo() hilighting object in wrong location
Description
This message was sent from www.opencascade.org forum user EricThompson
<[email removed]>
http://www.opencascade.org/org/forum/thread_19009/
------------------------------------------------------
I'm having a problem with object hilighting in some cases. It works fine in 3 of
my OpenCascade views, but is offset vertically in a 4th view. ( Each view is
viewing a seperate interactive context. ) The amount of offset is proportional
to the view scale.
I find that I can correct the problem by adjusting my y value as follows before
calling MoveTo():
double scale = (*myView).Scale(); // Odd notation because using an arrow does
not post to forum well
y = y - (int)(0.65*scale);
This hack is working, but if anyone can tell me what I'm doing wrong that is
causing the error, I'd prefer to fix it right.
Thanks!
<[email removed]>
http://www.opencascade.org/org/forum/thread_19009/
------------------------------------------------------
I'm having a problem with object hilighting in some cases. It works fine in 3 of
my OpenCascade views, but is offset vertically in a 4th view. ( Each view is
viewing a seperate interactive context. ) The amount of offset is proportional
to the view scale.
I find that I can correct the problem by adjusting my y value as follows before
calling MoveTo():
double scale = (*myView).Scale(); // Odd notation because using an arrow does
not post to forum well
y = y - (int)(0.65*scale);
This hack is working, but if anyone can tell me what I'm doing wrong that is
causing the error, I'd prefer to fix it right.
Thanks!
Public activity
3 archived notes
Participants are labeled by their role within this record.
Sergey,
Could you check the problem.
Could you check the problem.
Dear szy,
Can you please ask the topic starter to check if the problem is still reproduced in his application with OCCT 6.8.0 beta?
In fact, we do not have any information about his application design and thus cannot reproduce the problem ourselves.
Can you please ask the topic starter to check if the problem is still reproduced in his application with OCCT 6.8.0 beta?
In fact, we do not have any information about his application design and thus cannot reproduce the problem ourselves.
Sergey,
Author of the post doesn't answer to the request.
Taking into account that the initial post dated by 2010 very probably that the issue is obsolete for him. Therefore I suggest to define the next possible actions in frames of the issue according you own understanding.
szy
Author of the post doesn't answer to the request.
Taking into account that the initial post dated by 2010 very probably that the issue is obsolete for him. Therefore I suggest to define the next possible actions in frames of the issue according you own understanding.
szy
Related records