Manofjesus
-
Posts
142 -
Joined
-
Last visited
Posts posted by Manofjesus
-
-
Exactly, what i was looking for. In Corel it looks like PUT IN CONTAINER. But your suggested solution is also easy. Thank you, Mick, for fast response
-
I have a question, explained detailed in my screenshot. I want to add some volume to the flat layers by adding some shadows effect, but i need to keep this layer effect inside the figures perimeter. How this can be done in right way?
-
Somehow i face similar issue, but only on my desktop, not check this in start menu. Also in Windows 10, x64
-
I also found - it is impossible to install, when the Windows 10 vars TEMP and TMP are changed to the RAM drive. This changes not affecting for installations of other software, but affected Affinity Photo. Also affected for beta 1.7.2.464
-
Found annoying bug. As RAM becomes more and more affordable - it is good to use it for different purposes, not just for "let it be bigger, cheaper and faster"
So i successfully using ImDisk for that purposes for awhile. ImDisk has ability to change or redirect system variables TMP and TEMP to the RAM drive.
The Windows 10 defaults for variables TMP and TEMP:
%USERPROFILE%\AppData\Local\Temp
%SystemRoot%\TEMP
After creating RAM disc i can change it to - R:\Temp, where "R" - drive letter for RAM disc. ImDisk make this setting very handy to use. I install with such MOD a lot of software without any issues. But when i try to install AffinityPhoto beta or release version - it just stops without any clarifications. Until i switch back to Windows defaults, then installation process goes as intended.
-
It is the same as in last release version. It is equally to 180 degrees of rotation. Is this intended or not - i don't know, but it is not beta version bug for sure
-
The behavior of opacity slider is strange by itself. I move it left and right, while on your background layer - and until i loose the mouse button - the engine do not updating opacity state. This is weird anyway.
-
-
And for me works ok. Just test it again - work as expected.
-
Is it possible to solve such issue - as alignment object with the their axis of rotation, not as object bounds centers?
-
Here is some other brush work in progress. Update will arrive soon )))
- Lars Bergström, NilsFinken and Przemysław
-
2
-
1
-
On 7/14/2018 at 11:27 PM, R C-R said:
..... it will always have the same internal pixel dimensions (its height & width in pixels) regardless of those transformations
Let this object be as it is - i am not arguing about such concept. This is not issue at all, i am start my question not about this. Forget other commands - only COPY and PASTE. But the same or similar way it works in Photoshop - but in Photoshop i can copy a region from such non rasterized image layer with built in bitmap - that easy to check. There was no talk about transforming such layer. It is already projecting inner content to the dimension of my affinity working file. So my selection region, for example 200х100 pixels selecting exact region of that projection, the same content as i can see it in 100% percentage. If Affinity is projecting this bitmap information for me to see, already scaling it for my end resolution of my working file (the inner genuine resolution still can be different for sure) why not let me copy that region - no transformations just copy information that i see already in my working file? When you making screenshot of any information in your screen - it just copy, as it projected to your PC screen. I am talking about the same equivalent easy copy procedure.
-
toltec, i familiar with Adobe PS since SC2 and with Corel since version 7 in early 90xx. I understand MODULES or editing modes, or PERSONA's - but your idea about
6 minutes ago, toltec said:Can you edit an InDesign file in Photoshop, or edit a Photoshop file in InDesign?
is not applicable here - as i don't ask for editing some alien format or alien data inside AP - is not it? We talk about bitmap. Does it in container or not - it is bitmap and it is already inside AP. Since AP importing plugin understands and reads and accept some bitmap file - it is ready for manipulation inside the AP environment. Right? And here it place for this
11 minutes ago, toltec said:some things have to be changed in the way they work
That is subject i am talking about
-
dominik, i also hope for this - but as for me, it is even not function - it is like DNA - the basis (at least it has to be)
-
I dont want it to be clone, that is why i bought it - but NEW WAY not has to be LONGER way or LESS HANDY way - it has not to be
counterproductive. The disability easy copy in this scenario - i can't accept this feature implementation as NEW WAY - as it is not ergonomical and non logical. It is not mean - that i dont like the product - but want the improvements. -
Again, i understand idea to putting image to container. I appreciate such feature both - in PS and in AP. But i want to copy from such layer by my selected region with selection tool. This is straight plain and logical - this is plain common sense. The AP has just to virtually rasterise underlying image, copy some data from it according to my selection and then paste it - period. Why i need to make duplicate - > rasterise duplicated layer - > After copy and paste delete duplicated layer - why not to automate and hide all this steps from me in just COPY and PASTE way, as it is native in PS ?
-
The behavior in PS - i can paste bitmap or or use PLACE... as container - no problem. And when i making selection and copying - no any limiting. I can copy and paste from this selection. And no matter the underlying layer is plain raster image or raster image in container (placed with command PLACE..) But in Affinity photo - what the reason to prevent copying in the same way? I want to leave the image as it is and don't want to rasterise it, but want to copy some portion from it - is it wrong idea or behaviour? Until i make command RASTERISE - it copy whole layer and ignoring my selection area. Also when i CUT i just completely removes layer - not selected region. If it not possible - why the AP allow me to use selection tool on this layer? This is non logical. Keep in mind - that for many users the AP is a step from PS.
-
-
I understand that also in PS. I can just place an bitmap as layer or can place it as container. The behavior in PS - i can paste bitmap or or use PLACE... as container - no problem. And when i making selection and copying - no any limiting. I can copy and paste from this selection. And no matter the underlying layer is plain raster image or raster image in container (placed with command PLACE..) What the reason to prevent copying in the same way but for Affinity ? I want to leave the image as it is and dont want to rasterise it , but whant to copy some portion from it - is it wrong idea or behaviour?
-
Ohh man - thank you - but why is so non logical especialy for old PS user? What the wisom of doing it in this way? Image is not raster? Strange
-
Today i was trying to make simple editing by just copy (Ctrl+C) some rectangular area from bitmap layer and then past it (Ctrl-V) - but i lost my mind, what is wrong. The selecting area is ignoring and pasting the whole layer, work as duplicate. During the selection i try to select EDIT/CUT - it deleted the whole layer. What is it? So basic and primitive operations ....
-
-
Hello, friends. I am thinking about protection screen for my Ipad Pro 10.5 - but i am not sure about sensitivity and Apple Pencil response in AP after such screen installation. Do you have some pros and cons or some practical feedback for this subject?
-
Strange sliders behavior. Even short tap opens the numeric value window and then back to previous state, ignoring the value that i was tap on. I check only this issue in HSL colour mode only - but this could be in another sliders also.
P.S. Sorry for blurred video.
How to hide unwanted part of effects on layer?
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
Affinity is awesome piece of software, many thing it has from the start, but Corel not implementing a lot of easy (but usefull) things for decades.