Jeremy Bohn Posted February 8, 2019 Share Posted February 8, 2019 If I reposition the document origin away from the top left corner of the document and then drag to create a new guide, the position of the new guide has a tag that pops up next to the cursor which ignores the new origin's position. In the attached screenshot, you can see that the the 0 position on the rulers (the origin) has been moved away from the corner. The cursor unfortunately doesn't show up in the screenshot but you can see the little black tag reads 61p - it should be 0. A_B_C 1 Link to comment Share on other sites More sharing options...
A_B_C Posted February 8, 2019 Share Posted February 8, 2019 Good catch! Link to comment Share on other sites More sharing options...
Staff Sean P Posted February 8, 2019 Staff Share Posted February 8, 2019 Hi Jeremy Bohn, This is a known issue that is with development to be fixed! Link to comment Share on other sites More sharing options...
Jeremy Bohn Posted February 9, 2019 Author Share Posted February 9, 2019 Not fixed in build 238. Link to comment Share on other sites More sharing options...
walt.farrell Posted February 9, 2019 Share Posted February 9, 2019 6 hours ago, Jeremy Bohn said: Not fixed in build 238. We didn't expect it to be fixed in .238, as it wasn't listed in the release notes -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Jeremy Bohn Posted February 9, 2019 Author Share Posted February 9, 2019 I didn't know what we were expecting, only that it is a known issue. Link to comment Share on other sites More sharing options...
walt.farrell Posted February 9, 2019 Share Posted February 9, 2019 3 minutes ago, Jeremy Bohn said: I didn't know what we were expecting, only that it is a known issue. We (at least, I, since I probably shouldn't speak for everyone) expect that bugs which are fixed are announced in the release notes, and that if the release notes do not say that the acknowledged bug was fixed, that it hasn't been (Otherwise, we would all feel obligated to check, on every new release, whether any/all of our reported problems were still problems.) (I also think, that Serif expects us not to expect that something was fixed if they didn't tell us that it was. But I really can't speak for them.) carl123 and mac_heibu 2 -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. iPad: iPad Pro M1, 12.9": iPadOS 17.4.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.4.1 Link to comment Share on other sites More sharing options...
Recommended Posts