Jump to content


  • Content count

  • Joined

  • Last visited

About Friksel

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. Friksel

    problem with expand stroke....

    This, and the fact that developing new features is much more fun than repairing (complicated?) stuff that never worked.
  2. Friksel

    problem with expand stroke....

    Not only with creating icons. I'm having this issue all the time, also on bigger illustrations
  3. I see ctrl+shift+N is inserting a pixel-layer, but I'm working with vectors, so is there also a keyboard shortcut or button to insert a 'normal' vector-layer?
  4. Thanks for your reaction, but I don't want to paste something inside some graphic. I just want to add a layer inside another group, so only hierarchial.
  5. @haakooNot sure what you mean. I never seen an 'insert inside button' in Designer, neither does ctrl-alt-n does anything here (using designer BTW I'm working mostyl with 'normal' vector layers in Designer
  6. It would be great if there was some (context menu) feature to add a new layer inside the selected layer or group. I'm doing that a lot and now this takes way too much time when having lots of curve-layers, because the new layer is inserted way up. Now it goes like this to add a new layer inside a new layer: - add a new layer - find your layer --> with hundres of layers/curvelayers this is a looot of scrolling each time, because the new layer is added on top somewhere (I am always searching where it is) - move your layer all the way down to paste it inside the layer you want to paste it in It would be a lot easier if we could just insert (or paste) a layer inside the layer or group we have selected in the Layers panel. And it would be fantastic if there would be some keyboard shortcut, like holding shift while clicking 'add new Layer' button or something. That would speed up the workflow a lot. For everything above the same wishes for pasting Layers. That could work the same.
  7. Hi, I like the feature to select layers and group them and for some usecases that is great, because you can easily select those layers at once always. But a lot of time I want to group layers, but not with a group, but as children of a new Layer object (instead of a Group object). This is because Layers still have the ability to select children inside from within the viewport, while Groups can't do that. I find myself converting groups to layers and back sometimes, because for one usecase I like to be able to select all sublayers, while sometimes it's better to use all 'as one' and want to have it grouped. Right now converting between groups and layers isn't possible, so we need to add a new layer and drag all groupchildren inside and remove the group. A feature in the contextmenu to convert a Group to a Layer (as a group) would be very welcome. And also visa versa.
  8. Hi @GabrielM. Thanks for your quick response. It seems like when adding a new layer with a grouplayer selected Designer always inserts the new layer on top of the layer stack. So I have these questions now: 1) How can we add a new layer on top of a grouplayer (so have the same behaviour as insert a layer on top of another 'normal' layer) without dragging layers? 2) How can we add new layers inside other layers without dragging? 3) How can we add new layers inside layergroups without dragging? 4) Does every rule to add a new layer also works exactly the same when pasting a layer? 5) Are there shortcut keys we can hold to do things like insert a layer after or inside another layer? Thanks
  9. Hi, sorry for this newby question, I see myself struggling on where layers get inserted when adding new layers and it looks like to me it's placing on counter-intuitive places meaning I can't seem to get used to working with this after a long time using this software. So I want to invest some time in really knowing when a layer will be placed at what position on the 'layer-stack'. Does anybody here knows if there is a place where I can find some (hopefully official) info on this so I can print how this works in my head and finally get used to this? (my problem, I know, I should have done this way earlier). Thanks!
  10. Ah, I see what's causing this: the root layer was locked. Thanks for quick response @dutchshader
  11. just trying it, but doesn't do anything I'm afraid
  12. Hi, Does anybody here perhaps know what could cause my layers don't get selected when clicking on their graphic in the viewport? It's pretty difficult to keep on iterating over all layers everytime just to get the one I need. I'm used to click or double click on a curve to select the layer, but somehow this isn't working anymore. Is there some setting I'm missing here or something?
  13. You seem to not wanting to read and understand my posts. I discontinue this discussion now.
  14. No, not at all. It only needs to be implemented the right way: at the end of all snapping options. No matter how many options you have or whatever combinations you make with them; snapping to pixels should always be the last stage after all snapping options calculated. And yes, there is ALWAYS a priority order of snapping options, because that's just the way code works. When you move your node the software iterates somehow over all snapping options and picks some option that suits best or a combination of options are calculated together to get a result, but you always have a position value at the end of the equation somehow. And that value should only then be FORCED to a whole pixel. Where all inbetweens of a curve lie doesn't matter, you only snap nodes to pixels.
  15. I don't agree with this being moved to feature requests, but that should be obvious by my post. Next to this you explain how things are working now, but I know how things are working now. Thing is in my opinion it shouldn't work like this. Snapping to pixels is not something we like for layouts, but to be able to have our fills on exact pixels as far as horizontal and vertical goes. That should never be influenced by other snapping tools, that are used for layout purposes. Because when they do, like Designer is working rightnow, you simple cannot rely on 'Force Pixel Alignment' as a designer, because in way too many scenarios it's just not snapping to pixels and as a designer you don't even know that it isn't working when designing, because you only see it when zoomed in or happen to know this problem. I'm starting to wonder if people realy understand the purpose of this switch. We can talk about all kinds of scenarios with all kind of snapping functions turned on or off, but that doesn't hit the point here. Thing is that snapToPixel should snap to pixel. Nothing more and nothing less. And right now in most snapping-configurations it is not snapping to pixels. Which I call an issue. It doesn't matter how snapping functions are set, in the end in Force Pixel Alignment (snaptopixel) should always be applied in the end. And if a designer decided to turn on snap to the center of a curve or whatever else snapping function and that happens to result to half a pixel, then the same applies as when a user has his cursor on a half pixel: round it to a whole pixel. It doesn't matter if Designer choses the left or right one if it's exactly in the middle of 2 pixels. The only thing that matters is that it's always calculating in the same way. To either exact half pixels all chose the right side, or they always chose the left side. That way we can finally work on whole pixels as designer and use snapping options too. That is just impossible right now.