Jump to content

Malcolm Mactavish

Members
  • Content count

    6
  • Joined

  • Last visited

  1. Hi. I just installed 1.7.1.399. I placed some text on layer 1 - this contained words that the spellchecker didn't recognise. As expected, the red squiggled line was shown. I created a new layer 2 immediately above it, and placed a shape on this new layer (I was using a simple rectangle). The shape overlapped the text on layer 1. The red squiggled line from the spellcheck on layer 1 was visible through the shape on layer 2. This is apparent whether placing the two elements on separate layers or on the same layer, and irrespective of the opacity setting of the "upper level". I tried a test (attached) which gave the same result. This may be the correct/desired behaviour, but I haven't noticed it in previous versions. Hope this helps. spellcheck highlight showing through layer above in stack.afpub
  2. Malcolm Mactavish

    Items remain outlined after deselection

    Forgive my lack of understanding, but let me see if I understand this. For raster files, I use quite an old version of PhotoShop which still meets all my needs. In that. I'm working with pixels. In DrawPlus, etc. and now Affinity Designer I'm working with shapes (in Draw Persona), which are vectors. OK so far? Draw Persona is a vector mode. I've never used Pixel Persona, so hadn't come across a pixel selection in the context of AD. I looked it up in the help file and, under "Creating pixel selections", the file says: To paint a pixel selection: From the Tools panel, select the Selection Brush Tool. Adjust the settings on the context toolbar. Drag on your page. To create a pixel selection using a Marquee Selection tool: do this and that To draw a pixel selection: do this and that To create a pixel selection from a layer: do this and that From my reading of the help file, using pixel selections, means (obviously) that I'm working with pixels. In turn, my understanding is that to work with pixels I need to be in Pixel Persona, or perhaps in Draw Persona but working with a pixel-based artefact such as a photograph. If I'm correct thus far, then if I'm in Draw Persona and create a shape using the geometric shape tools or text tools, I'm working with vectors. Is my understanding correct up to this point? So here's what I've done to try to understand this: 1) In Draw Persona, I took my "deselection2" file and added a raster item (a jpg image). If I select this and delete it, there are no marching ants. From my previous work in AD, this is what I would expect. 2) I switched to Pixel Persona, added a selection and used the paint brush tool to add a few squiggles. I hit the delete key and the contents of the selection were deleted, but the selection was retained, as shown by marching ants. I think this is what you are referring to in your most recent reply. 3) If I stay in Pixel Persona, add a new selection, the first selection is deselected. And if I add some colour inside selection 2, then deselect it, the marching ants are still showing the area taken up by selection 2. I can see that this matches your description as well. 4) If I revert to Draw Persona and add a new geometric shape, the pixel selection remains selected - just as you predicted it would, 5) Interestingly, the item that was NOT being deselected (the item in the original file I supplied) was deselected at point 2. As soon as the rectangular marquee tool touched the design, the original (vector) selection disappeared. Perhaps, in some isolated cases, vector items are being treated as pixel selections? I think there are a number of observations here: a) The processes in steps 1-4 include a mix of darw persona and pixel persona operations. The results ARE as you predicted in your latest reply. BUT ... these are not the operations that I follow when experiencing the "failure to deselect" problem. b) You are, quite naturally, looking for an answer as to why I am experiencing this issue. You're finding a match in "pixel selection" and concluding that this is where I'm going wrong. c) I'm coming from the angle of a realtively novice user of AD, but a sophisticated user of interfaces in general. From that perspective, I've got no "baggage". If you'll forgive my audacity, I think what is happening is that you're seeing the pixel selections as a match for the problem rather than looking at the symptoms and asking whether this could be something else. Going back to my previous post, if this "failure to deselect" is a design feature then, because I use AD at some point almost every day, I'm sure I would have realised that this was happening under a given set of circumstances. I would be able to predict when it would happen and learn how to resolve the matter (i.e. it would become a "conditioned response"). The reason that I'm convinced it IS a bug is my point about consistency. If it's a design feature, the failure to deselect would happen every time I perform a given operation. If it happens less than 1% of the time I perform that exact same operation, then the behaviour is not consistent or predictable, and is unlikley to be a design feature. I do a fair bit of user testing and entirely understand that we like to be able to follow a defined set of inputs and observe the outcomes. If there was a set procedure that induced this issue, I'd be more than happy to reveal it. The simple fact is - and I apologise for restating this - the issue happens very rarely. So rarely and unpredictably that I can't think of a way to backtrack and replicate the conditions that induce the problem. If I can't replicate the problem, then it can't be consistent. And, in my view, if a behaviour isn't consistent AND can't be predicted, then it's an abnormality. I truly hope this helps. deselection_3.afdesign
  3. Malcolm Mactavish

    Items remain outlined after deselection

    With respect, that's just nonsense. Here is another version of the same file. In it, I have added a simple shape (vector). If you select the shape with a primary click and hit the "delete" key, the shape is deleted and the area previously occupied by the shape is deselected. There are no "marching ants". this is the behaviour that I experience with 99.999% of cases where I select and delete an item. I work almost exclusively in "draw persona" and have experience the "marching ants" phenomenon with shapes and text. From what you say, the selection persisting in the form of "marching ants" is, to use a Microsoft phrase, a design feature rather than a bug. If so, then - adhering to the "consistency" factor of usability - surely the "marching ants" would be present every time an item is selected and delete? Also, if one item is deleted and the "marching ants" indicate that the area is still selected, then when another item is selected, surely the previous selection would be deselected? Certainly, I can see no use case for a context where a deleted item remains selected until proactively deselected - especially one where the selection persists following the deselection of subsequent items that themselves do not persist. I would also expect (from the perspective my own mental model - which I accept may not be your mental model) that if all layers and items are deleted from a file, there should be no residual selection of an item that was deleted several generations previously. If my mental model and my interpretation of apparent general behaviour of the program are seriously misguided, can you tell where and why I have an incorrect interpretation? deselection_2.afdesign
  4. Malcolm Mactavish

    Items remain outlined after deselection

    Thanks. I do understand how to deselect an item (I'm using the term "item" because, as you know, in coding "object" has a particular meaning which isn't necessarily applicable in this case). Can I perhaps give additional clarficiation. In my original post, I said "after I have deleted an item (e.g. a pieve of text) in Affinity Designer, the "marching ants" continue to show the item". So it's not a simple case of an item not being deselected. What I tried to explain is that, on occasion, when I delete an item, it is not "deselected". It remains on the display as "marching ants". Normally, I when I delete an item, it is then deselected. This normally works as intended, but occasionally it doesn't. I can, as you say, use the keyboard shortcut "Esc" to manually deselect the deleted item or, as I discovered this morning, I can use the menu item "select/deselect". But, since deleted items are normally deselected automatically, there does seem to be a particular condition in which a deletion fails to be fully executed. This is when the symptoms in my original post become apparant. The "marching ants" remain in their position, are influenced by the zoom setting, etc., but the "deselected" item cannot be reselected using either a primary or secondary click - or via the "ctrl+alt+]" keyboard shortcut. Divide operations don't take effect either, and trying to perform an operation on it (e.g. rotate) results in the underlying item being altered and the "deselected" item remaining unchanged. So it seems to me that the "deselected" item has actually been deleted but isn't being deselected on the display. I've attached a file that contains a "deleted but not deselected" item - hopefully this will let you see what I am talking about. deselection.afdesign
  5. Malcolm Mactavish

    Items remain outlined after deselection

    Additional note: After some more testing, I found that, while the failure to deselect takes effect when using the mouse, the "problem" item can be deselected from the menu (select/deselect). Irrespective of which (if any) layer/item is currently selected, the "problem" item is deselected.
  6. On a small number of occasions, after I have deleted an item (e.g. a pieve of text) in Affinity Designer, the "marching ants" continue to show the item. This persists even after the file is closed and reopened, after Affinity Designer is closed and restarted, and even after the computer is shut down and restarted. If all items in the design are deleted, the marching ants still persist. If the artboard is deleted, they persist. The only way I can find to remove them is on a design with multiple artboards - deleting all artboards other than the first or last will result in a single artboard design with no marching ants. It's very peculiar. It very rarely happens so I can't describe the actions that lead to the issue.
×

Important Information

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.