change all to Black

[silverlocks]

Having imported parts of a colored PDF file I now want to change my Affinity file to save in Black only. is there a way of selecting all and then just doing it

Pixie.afdesign

[stokerg]

Hi Silverlocks,

 

You could select all the layers and groups, then select the Stroke colour to black.  However, the 2 images you have inside the circle are causing all manner of problems on my Mac and Windows PC.  Also had my Supervisor test it on his Mac and the same happened to him.  I had to move both of those images outside of the group they had been in and then i could apply the stroke colour of black.  But i was able to get the attached results with the images out of the group. 

 

Why those images are causing me issues, i've no idea but will give the file a bit of a poke and see if i can get to the bottom of the problem.

Pixie stroke colour black.afdesign

[JimmyJack]

@silverlocks If you mean every element has to be all black... You can select all your groups and hit FX color overlay. The default is black.

But if you mean everything has to be a value of black, you can just switch the document to be grey (8 or 16 bit). Or, if you still want color elsewhere, group everything with a B & W (or HSL) adjustment. 

 

Edit: To sidestep the odd behavior discussed below, you could of course just select everything then deselect the two graphics and do what Stokerg said... just set the stroke to black. So that would be: CMD drag select all the individual elements > hold down shift and click on the two graphics to deselect them > set stroke color.

 

@stokerg Seems like this bug is more than just this document. It happens for me on any file with any curve & pixel layer combination.

New doc > draw curve (or shape) > make pixel layer (doesn't even need to have anything in it) > select both > try and change stroke or fill.

[R C-R]

12 minutes ago, JimmyJack said:

New doc > draw curve (or shape) > make pixel layer (doesn't even need to have anything in it) > select both > try and change stroke or fill.

Hmmm. For me, if I do this the stroke of the curve or shape changes without problems. Changing the fill changes the fill of the shape without problems & fills the (empty or not) pixel layer with the same color.

 

What happens when you try?

[stokerg]

52 minutes ago, JimmyJack said:

Seems like this bug is more than just this document. It happens for me on any file with any curve & pixel layer combination.

New doc > draw curve (or shape) > make pixel layer (doesn't even need to have anything in it) > select both > try and change stroke or fill.

 

Like for @R C-R that process works for me.

 

But the file from Silverlocks certainly has the problem.  I've tried the file on 3 different Macs now and all cause Designer to lock up.  If you can create a file that causes the same issue, please do post it, as it should also cause my Designer to lock up and i'll have another file to hand over to the Dev team with the same issue, if one of them doesn't spot this thread before tomorrow  

 

 

[toltec]

11 minutes ago, stokerg said:

 

Like for @R C-R that process works for me.

 

But the file from Silverlocks certainly has the problem.  I've tried the file on 3 different Macs now and all cause Designer to lock up.  If you can create a file that causes the same issue, please do post it, as it should also cause my Designer to lock up and i'll have another file to hand over to the Dev team with the same issue, if one of them doesn't spot this thread before tomorrow  

 

 

 

For what it is worth, the file locks up two PCs for me. One Win 7, one Win 10. Not that that should matter. Designer 1.6.1.93

 

[JimmyJack]

1 hour ago, R C-R said:

What happens when you try?

 

 

49 minutes ago, stokerg said:

 

Like for @R C-R that process works for me.

Both stroke and fill result in replacing the pixel layer with basically a Fill Layer a la AP. Is this what you want??

Consider this. If I have a rectangle, rasterize it (now pixel) and click on and/or change the fill, nothing happens (as it should).

The pixel rectangle shouldn't be replaced with a canvas of color.

 

This is what's happening for me with the OP file. Curve + pixel selected > click on stroke color black > the whole page turns black.

And with a bit of a hang up too.

 

[R C-R]

50 minutes ago, JimmyJack said:

Both stroke and fill result in replacing the pixel layer with basically a Fill Layer a la AP. Is this what you want??

For me, changing only the stroke affects only the curve or shape, but not the pixel layer. Setting the fill affects both, but I halfway expected that because both are selected. However, I do see what you mean about inconsistent behavior when both are pixel layers.

[lepr]

.

[stokerg]

1 hour ago, JimmyJack said:

Both stroke and fill result in replacing the pixel layer with basically a Fill Layer a la AP. Is this what you want??

 

 

Okay, there has been a small misunderstanding, you got further with the file than i did.  As soon as i selected the all the layers and tried changing the colour in the original file, my machine(s) locked up.  I tried the combination you posted and it didn't lock my home iMac up, but it did turn the whole page the colour i selected. At this stage, i was just looking for the lock up, which didn't happen.  I'll re-test in the morning on my office iMac. As also confirmed by @R C-R i get the inconsistent behavior.

 

3 minutes ago, owenr said:

When a fill or stroke colour is applied to a Group, any Pixel object in the Group is completely filled with the colour.

 

Thanks for that, i wasn't aware it's already been talked about.  I'll have to check this in the morning, only reason i say that, is you don't need to group them.  This behaviour is happening without the group. I can't say i know enough about Designer to say if this is expected behaviour or not.  I'll check with the QA team in the morning and if need be get one of them post and explain what's happening here  

[lepr]

.

[stokerg]

3 minutes ago, owenr said:

I cannot imagine why that would be designed behaviour, and now doubt the correctness of the information we previously received about grouped Pixel objects.

 

 

Without seeing that post, it's hard for me to comment.  I'll get QA to go over this thread tomorrow and either i'll update here or they will  

[JimmyJack]

10 minutes ago, owenr said:

I cannot imagine why that would be designed behavior,....

 

Thank you. Me either.

 

FYI @stokerg (et al)..... also happening in Photo with it's quasi-vectors, shapes and image layers.

[stokerg]

Just keep this thread updated:

 

QA logged this with the Dev team today, so they have the original file to look at the locking up issue.  

 

They also put in a separate request for more information on what's happening with the issue raised by @JimmyJack 

 

As soon as i've more info i'll update here