Jump to content

Gear maker

Members
  • Content count

    994
  • Joined

  • Last visited

Everything posted by Gear maker

  1. Are you running AD in Separated Mode? If so this is normal that it appears to not open but with a cmd + tab it then shows. What I do when I start AD is to right click on AD icon in the dock then left click to select the Recently Open file I intend to work on. Or you can cmd + tab after clicking on the dock icon. Or you can click on the AD in the dock a second time. I hope that helps.
  2. I'm not sure if this is what you are after. In Designer you can take any shape, one you've drawn or something from the shape tool. Say a star, then convert it into a text path (Layer>Covert to text path) then add any text using the text tool.
  3. I really love being able to turn on the Use ⇧ modifier to cycle tools, it used to be so awkward to hit a hotkey for a tool only to find you were already in that tool and now are no longer there because you were switched to the previous tool used. But the cure has just shifted the problem. I just hit a G when I happened to already be in the Fill tool. So now instead of switching my tool selection to the previous used it searched out the layer that had a name starting with a G and selected it instead. So now I changed the gradient in the wrong layer. Okay so now how do we stop AD from searching out a field with the name starting with the hotkey that is disregarded by the tool cycle? The only workaround I can think of is to start every layer name with some character that doesn't cause a tool cycle like maybe a tilde. Or just don't name layers, which is really a poor solution. I didn't even know AD would search out layer names starting with a character pressed until this happened.
  4. In Affinity Photo there are a couple ways. Go to the View tool (hand) and in the tool bar there is a "Units" field which can be set to inches. You can also do it in the menu Document>Resize document.
  5. vicentlepes, thanks for getting the video to Sean, I was having problems with QuickTime. Sean, yes I always run in Separated Mode. I guess I should mention that as this isn't the first time it has been important. Mike
  6. MEB, a video doesn't show the problem well as you can't see keystrokes. I thought you were able to reproduce this back in April. We have been waiting to stop the cycling of tools for years and now there is a way but it causes a worse problem. Did you try my example with the test4 file I had attached above in April? With Use ⇧ modifier to cycle tools selected: Several things seem to trigger the problem, one of those is to: Click in the area of the layer panel below the layers to unselect all layers Then click on the unnamed layer Press a P twice you'll end up in the Pen tool but the layer selected now is the Purple layer, even if you wait a few minutes between presses Press G twice you'll end up in the Fill tool but layer Gray selected Press M twice you'll end up in the Rectangle tool but with layer Marble selected Press A twice you'll end up in the Node tool but with layer Apple selected The idea of the Use ⇧ modifier to cycle tools is supposed to be so that if we happen to hit a letter key more than once it doesn't put us in a different tool than what that letter calls for. If we forget we are already in the Pen tool than hitting a second P won't dump us into the Brush tool. And now it doesn't, but frequently the second P will switch to a different layer which I think is worse because we end up modifying the wrong layer or creating a layer in the wrong location. You are right it's not every second keypress, but it happens frequently. It used to be that when I pressed a P I would have to look at the tools or at least the cursor to see if it was correct. Now we have to look at the layer panel to see if the correct layer is still selected following the keypress. Not what I'd call forward progress. Unless we always have all groups expanded then searching by the first character of the layer name isn't a reliable method of finding a layer. And I usually don't keep everything expanded. Mike
  7. It could be just pressing tab which erases toolbars and panels. Then tab shows them again. It could be shift cmd H which hides just the studio of panels, menu View>Studio>Hide Studio or shift cmd H again. Do either of those work for you?
  8. There is a preference that can be used to affect this. But with the default if you hold down the opt key (on a MAC) the wheel will cause zooming. With out the opt key down you'll get vertical scrolling and with the shift down you'll get horizontal scrolling. The preference can set it so that the wheel just does zooming. I don't think you can do scrolling if this is set, but I've never tried it.
  9. eobet, did you mean the keystroke? Use a ctrl + 2 or cmd + 2 to get a 200%, a 3 gives a 400%, etc.
  10. Check the following:
  11. craiigman, I would guess from this image that you have a shear specified. May 6 or 7 degrees. With out having the file that would be the obvious guess. Check on the Character panel. I over laid a star shape just to make it easier to see. When I recreated it but making sure there was no shear but with the same font and size it looks good.
  12. This was created in AD 1.7.1 It has 2 text fields one stating "100" and another stating "50". Why is the "50" text not visible? Color, size, visibility, position, stroke, etc. do not affect it. Anyone have an idea what is causing the 50 to be invisible? In the node tool the outline is visible but that's about the only way to make it somewhat visible. test50.afdesign
  13. Mark, in a new document text seems to be working. But if I copy any fields from the original document that aren't visible then they aren't visible in the new document. In my original document after a half dozen fields not visible I ended up doing the Defaults>Factory Reset suggested by Bruce and now it seems to be working fine.
  14. Bruce, but both show they have No Style. Which I have been told many times by my wife, but I digress. I know if I copy the style from the 100 to the 50 it then works. So you think it was just a fluke? This was the first text field I created today, other days they all worked fine.
  15. Gear maker

    New node point?

    That description meant nothing to me. I had to use it to figure out what it actually did or didn't do.
  16. Gear maker

    New node point?

    evtronic3, first thing to remember about the smart node is if you make almost any change to it's handles it will change into a smooth node. It's how it interacts with it's neighboring nodes that's important. Make a shape with several nodes, convert them all into smart nodes. Then grab one and move it, you will see that the handles on the neighboring nodes change to keep the curve between them as smooth as possible (in a smooth node they don't move). Which will change the paths on either side of those nodes to change some. Hope that helps. Mike
  17. This can be really handy but be careful it is very unreliable and unpredictable. My original: After just a copy and paste, or a duplicate: After trying to use tracking on the copy to get it back to the original. Tracking is set to -1000 here: The rotation of the objects around the text path are very different, even the distance from the center point have changed. As far as I have found there is no way to get it back to what it was without just starting over and recreating the entire assembly. So beware.
  18. I know this question has came up before but I'm not finding it with a search. In a design such as this there is only one path, but 3 of the nodes are in the exact same location. How can I grab one of the lower nodes in the stack? When I try I always get the same node. The only way I find to do this is to unstack the nodes moving the top one to the side, then move the second... But when I move the bottom one the original location of the rest is lost. I was thinking someone had come up with a way to cycle through the nodes in that position to reach the lower nodes but using a modifier key or something else. Can anyone share a method they have found to do this? I appreciate any help provided.
  19. JimmyJack, that's what I was looking for! Thank you. Now I have to remember it. Great.
  20. Thanks iaing, that's pretty much what I have been doing. One node I put one direction, the next one another, etc. Or I just make a copy of the object so that that location still exists, I can just drag nodes on the original until I find the correct one then drag the others back to where it belongs via snapping to the copy and finally delete the copy. No good way, but I was hoping someone had found a way.
  21. No it is only one path. This is just an example. My actual drawing is much more complicated. But I have the problem of more than 1 node in the same place on a single path. And I run into this every so often. Where I am needing to move the bottom node preferably without moving the top node. Sometimes it's my design and other times it's caused by doing an Add of 2 or more shapes.
  22. gdenby, good idea. Easier than counting the dashes. The user must remember to always subtract 1 from the count and then add back any partial spacing as the fraction.
  23. Hey I like it! Good one.
  24. FYI other points I have identified for measuring: 1 1 0 0 36pt = 1" between dashes 1 1 0 0 18pt = 1/2" 1 1 0 0 12pt = 1/3" 1 1 0 0 9pt = 1/4" 1 1 0 0 4.5pt = 1/8" 1 2 0 0 24pt = 1" 1 2 0 0 12pt = 1/2" 1 2 0 0 8pt = 1/3" 1 2 0 0 6pt = 1/4" 1 2 0 0 3pt = 1/8" 1 3 0 0 36pt = 2" 1 3 0 0 18pt = 1" 1 3 0 0 9pt = 1/2” 1 3 0 0 4.5pt = 1/4” 1 4 0 0 29pt = 2” 1 4 0 0 14.4pt = 1” I don't know if it will be different with a retinal display.
  25. Tokai, the second set of handles are for skew of the gradient. Below are a couple entries that might help explain. To trigger the second set you can switch to the Move tool then add a skew from the transform panel then switch back to the Fill tool. I also get this many times I copy a layer with a gradient. Double clicking on either of the second set of handles will remove the second set.
×