![]() ![]() I have seen this happen a couple times before, but never put together that the north arrow was linked to the viewport in every case I've seen this happen. My viewport just magically panned by itself, while locked, to 0,0 instead of staying where it was the last time I looked at this layout. You can clearly see the viewport is locked, yet the cursor is around -151.7,529.5. Here's a screenshot of my layout, with the cursor inside the model space. My drawing is around 3000000,745000, so it's not even a zoom extents type issue. In fact, my viewport is still locked at 1" = 40' scale, but it's panned to 0,0. I, too, have a plan view viewport that is using northarrow directly from the Layout Tools ribbon. I can simply not use north arrow feature under the layout tools to get by, but should I be reporting this potential bug somewhere? If so wrote:ĭid your viewport pan to 0,0 while still being locked? That's happened to me and today I ran into this issue again. The bug may be simply the custom block I am using not playing nice with the North Arrow feature under Layout Tools, or the program may not like the quantity of north arrows attached to viewports in each drawing ( I have 11 in one and 10 in the other). I am using a custom north arrow block that keeps the "N" vertical and rotates the arrow as needed. I should note that in the same drawings that my plan viewports bugged, my profile viewports did not (I assume because I have nothing attached to them). Now I have 2 drawings where I have had my plan viewports bug and in every instance I had a north arrow attached to the VP. This feature is under layout tools -> North Arrow. On each of my plan viewports I have a north arrow block attached to it that auto rotates to the north direction of what is being displayed in the viewport. I think I may have figured out what is causing my plan viewports to mess up and reset. I would really like to know what is causing this so I can prevent it from happening again. I am able to get around this problem by re-aligning my viewports to their correct position, its just annoying having to do this again. How is it even possible that they get moved if they are locked? This makes absolutely no sense because I wasn't working with the plan view viewports and I am 100% certain they were LOCKED. After I come out of the reload in my plan sheet drawing, every single viewport that shows the master plan xref was reset to a position way out in left field. As I am doing this editing, I am saving the profile master and reloading the plan sheet drawing. I was switching between the profile master and my plan sheet drawing doing some adjusting to the profile master's profile VC labels and making sure they will fit into the viewports I made in the plans sheets. To give you a little background, in my plan sheet drawing I am showing a plan view and profile view and I use 2 xrefs to do this, my master plan drawing and my profile master. In addition, it think it’s a fair assumption that read the viewport and immediately writing back to it should not cause a drift, whether the ruler is on or not.I know for a fact that my viewports were in the correct location, at the correct scale and they were locked. Here is a related bug my user filed on GitHub. The plugin replies on the accurate behaviour of the figma.viewport API. It calculates the x and y difference the viewport needs to travel and apply it as user controls the device. I maintain a beloved a plugin that allows user to use a custom device to zoom/pan the canvas. Reproĭocument.getElementById("set-viewport").onclick = () =>, "*") ![]() When ruler is turned on, the value read from and the value written into figma.viewport are treated differently. ![]()
0 Comments
Leave a Reply. |