Position of pasted nodes is off on non-default zoom levels

Having problems with IHMC CmapTools? Think you have found a bug? Let us know!
Forum rules
Before you post a problem or bug, please be sure you have included the version number of IHMC CmapTools, the operating system and version, the amount of RAM, and any other information that allows us to be able to replicate the problem you are having. (i.e. what were you doing when the problem occur? were you running another program (application) by the time you have the problem?)
Post Reply
vesjolovam
Posts: 5
Joined: Tue Nov 07, 2023 3:32 pm

Position of pasted nodes is off on non-default zoom levels

Post by vesjolovam »

Since many bug reports seem to stay unaddressed due to the efforts (not sufficiently compensated by funding) required to diagnose and fix them, I've decided to try and look into the program myself and find the cause of the problem. I do understand that this is a little against the rules, but I'm only trying to help the people interested in this otherwise great piece of software, and indirectly - to help you (the developers) officially help them with minimum efforts.

Judging from the debugging info (Windows, 6.04), CMapComponent.getViewableArea outputs in logical coordinates, while CMapComponent.getBoundsOfNodes and CMapComponent.getBoundsOfEntitys output in physical coordinates, and this causes (in CMapComponent.pasteFromClipboard) the nudge calculated for CMapComponent.moveGraphicalEntitiesBy to be off by an amount that is dependent on the zoom level, the origin of the copied items and the offset of the viewport. Applying CMapComponent.ComponentToMap to the output of CMapComponent.getViewableArea fixes the problem.
Last edited by vesjolovam on Tue Dec 26, 2023 5:21 pm, edited 1 time in total.
Jacobjsdhfg
Posts: 1
Joined: Thu Dec 21, 2023 5:42 am

Re: Position of pasted nodes is off on non-default zoom levels

Post by Jacobjsdhfg »

It's admirable that you're taking the initiative to investigate and address the bug reports in the software, especially when resources for addressing these issues may be limited. Drive Mad 2
cmapadmin
Site Admin
Posts: 805
Joined: Sat Dec 13, 2008 2:22 pm

Re: Position of pasted nodes is off on non-default zoom levels

Post by cmapadmin »

Thanks! Just passed your message to the programmer responsible for the code!
carinform
Posts: 2
Joined: Tue Dec 12, 2023 3:18 am

Re: Position of pasted nodes is off on non-default zoom levels

Post by carinform »

Jacobjsdhfg wrote: Thu Dec 21, 2023 5:45 am It's admirable that you're taking the initiative to investigate and address the bug reports in the software, especially when resources for addressing these issues may be limited. skibidi toilet
Thank you for sharing this blog with me. Using the CMapComponent.ComponentToMap to the CMapComponent result.The issue is fixed via getViewableArea.
SungBlakeman
Posts: 1
Joined: Mon Feb 05, 2024 2:07 am

Re: Position of pasted nodes is off on non-default zoom levels

Post by SungBlakeman »

carinform wrote: Wed Jan 03, 2024 1:33 am
Jacobjsdhfg wrote: Thu Dec 21, 2023 5:45 am It's admirable that you're taking the initiative to investigate and address the bug reports in the software, especially when resources for addressing these issues may be limited. rice purity test
Thank you for sharing this blog with me. Using the CMapComponent.ComponentToMap to the CMapComponent result.The issue is fixed via getViewableArea.
It's great that you're willing to contribute to addressing bugs and improving the software.
xerianussa
Posts: 1
Joined: Tue Feb 06, 2024 9:18 pm

Re: Position of pasted nodes is off on non-default zoom levels

Post by xerianussa »

Jacobjsdhfg wrote: Thu Dec 21, 2023 5:45 am It's admirable that you're taking the initiative to investigate and address the bug reports in the software, especially when resources for addressing these issues may be limited. Dino Game
It appears that there's an issue with the positioning of pasted nodes when the zoom level is adjusted from the default setting. This discrepancy in position could potentially disrupt the workflow and lead to confusion for users who rely on precise node placement.
Post Reply