Jump to content

gaufde

Members
  • Posts

    16
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I completely agree! Please add robust relative path support. To me, this seems like a relatively small software change that will make a huge improvement for users.
  2. Please fix this/add this feature! It would be a small change with huge advantages for the end user
  3. Hi Sean, I sort of figured that it could be an order of operations problem. I played around with it a bit more, and now I think I understand more about what is going on here. As I understand it, there are three linear transformations needed for the isometric grid: rotation, skew, and a transformation to elongate/squish along one axis. I tried applying each one in turn, and issues didn't arise until applying the "squish" transformation. It seems like this is the step where results between the curves and the rectangles diverge, which makes sense because "squishing" the shape should have different outcomes on curves vs a rectangle with clipped corners. Below is an image of two rectangles that started as squares with clipped corners. The one on the right was converted to curves before squishing. Obviously the results are different, which is the expected behavior in this instance. So, I think I now understand where the difference comes from and why it is actually the 'correct' behavior in each instance. I guess the question is, does it make any sense to try and get the clipped corners to act more like the curves when using the isometric grid feature because users might expect that? Correct me if I am wrong, but I think that all that is needed would be to keep track of the "squish" transformation applied to the object, which should be calculated based on the amount of skew applied. I would propose that this "squish" transformation should be remembered when using the isometric tools. I think that would make the behavior of the isometric grid more consistent from a user perspective as it would more closely mimic 3D space without actually adding another dimension to the program. Also the whole point of the isometric grid is to mimic 3D space, so I think that would be consistent with it's use case. I understand the mathematical simplicity of the transformations as they are, and I know I can flatten the shapes, but in my mind being able to keep them editable would be a huge bonus and way more powerful!
  4. I just found a little bug with the isometric grid feature when using rectangle objects that have corners applied to them. Below is a screen shot from Designer 1.9.3 on MacOS 10.14.6. Both objects started as squares with 25% straight corner clips applied. On the left, I converted the object to curves, and the right one is kept as a "rectangle". I then individually fit each object to the top plane of a 2:1 Isometric grid. You can see that the corners of the "rectangle" object on the right are not straight when compared to the corners of the object that was converted to curves (left).
  5. Hi, I have a little feature that I think would make using the appearance panel easier. It would be nice to be able to Shift-click and highlight multiple strokes/fills so that they can be edited simultaneously. This could be useful in the instance where I want to be able to quickly delete multiple strokes/fills at the same time, or change just one aspect of their appearance. For example, if I had five strokes and each had a different color, it would be nice to simultaneously set the opacity of all five strokes at once.
  6. Hi All, Thanks for the help and interest so far! I just did a few more tests to try and isolate the issue. First, it appears that the program crashes mainly when I have the move tool active while I use cmd+c to copy the layer. The conflict appears to be coming from keyboard maestro (8.2.4) , and so I was able to solve that issue in keyboard maestro preferences > Excluded > The following applications are excluded from the clipboard history unless you explicitly read the clipboard. I then added Photo to that excluded list. This made it so that my steps outlined in the first post no longer cause a crash; however, I haven't been able to test this more thoroughly with other files. It still seems like there could be some sort of bug present based on what Puck and madflute (from the other thread) have described.
  7. What strange behavior! This almost intrigues me more than the actual bug itself. Also, I found a similar thread right after I posted here. MEB's reply asks if the OP of that thread had any sort of clipboard managers/similar utilities running in background. I don't know about you, Puck, but I have Alfred and Keyboard Maestro (and some other utilities like Hazel) running in the background so it looks like I will have to try some more tests to isolate if any of them are causing issues.
  8. Hi, I don’t have any real answers for you, but I think I may be experiencing the same issue. For me it happens mainly with layers that have a mask on them. Your might want to try copying layers one at a time and copying the mask separately. I have had some success, but it’s been frustrating. Another idea I just came up with is that you could try copying and pasting the layers while in designer or publisher (if you have either of them). I haven’t tried this but maybe it could work? Anyways, I made a separate post about my issue this morning before I saw this thread. Maybe linking them together will help the developers. Best, Graceson
  9. I have been having some problems with photo crashing when I try to copy and paste layers between files. It appears to happen with pixel layers that have a layer mask. Here are the steps I use to fairly reliably get photo to crash: 1. Open a blank document 2. Use a large soft brush with low flow to paint around the canvas. I have been using black because it is easy to see. 3. Add a layer mask to the pixel layer and use the same brush to draw on it. 4. Select the pixel layer (including the mask) in the layers pallet and press cmd+c to copy 5. Photo Crashes. I have attached a crash report to help diagnose. Affinity Photo Layer Copy Crash Report.rtf
  10. Thanks for testing this! I just tried your exported pdf and the also used the pdf/x-1a preset to try exporting it myself. I printed each from Preview and both worked fine. However, when I was testing earlier, exporting using the pdf(for print) preset did not work well. I'm not sure why these would give different results, but I guess that is good to know. I will keep your suggestion in mind to print from other applications. However, I am still interested to see if my weird results can be reproduced by anyone. We have figured out a work around, now it might be nice to see if there is a printing issue in Publisher than can be fixed in a future update.
  11. The group up top is just two text layers that aren't interacting with the image at all. I tried playing around with that as well, but ungrouping the text had no effect on the images. The files are too large to upload here and I don't want to modify them too much, so I have created a dropbox link where you can download them. I have included the one with the problem, one that I have modified so that the image doesn't overlap, and the image that is linked from affinity photo. https://www.dropbox.com/sh/s0mo6ykbdpqrrx5/AABPxzn1QLKGeQLmpsThE3pDa?dl=0
  12. This is sort of what I was thinking. However, the text is above the image and so I don't see why it would need to be rasterized. I have text above an image on another page of this document and everything works fine there.
  13. I just found some very weird behavior while trying to print out a document from Publisher. I was printing my document and noticed that on the cover some of the text was printing with a worse quality than others: See how the first two lines of text appear bold? That is the issue, they are all supposed to be the same. So, I went hunting to try and find the problem. I tried exporting a pdf and printing from preview on my Mac. Doing that made all the text uniform, but the quality was bad for all three lines instead of just the two. After a bunch of trouble shooting, I noticed that on my document the image overlapped the first two lines of text that were having problems: So, I tried cropping the image so that there was no overlap and then printed it again. And...it worked! Now, I have no idea why the image overlapping the text would make any difference. So, I thought that I would share this here to see if this is a bug that can be reproduced on other equipment than what I am using. I have files that I can share if needed, however they are larger than the 512MB upload limit. Publisher 1.7.3 (trial version so I haven't tested the beta yet) Mac OS 10.14.6 HP M750 LaserJet Enterprise
  14. I think I just found a small bug in the Resize Canvas feature. When resizing the canvas by a small amount, say a change of 0.25 inches in one dimension, the constrain proportions feature doesn't work. Instead, only one of the document sizes is changes and aspect ratio isn't preserved. Affinity Photo 1.7.3, Mac OS 10.14.6.
×
×
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.