-
Posts
4,664 -
Joined
-
Last visited
Everything posted by Joachim_L
-
Visible text disappears when pulled over Object
Joachim_L replied to DBerlin81's topic in V1 Bugs found on Windows
I knew it happened to me a while ago. Yes, text can vanish due to settings of the Baseline Grid. See the picture. baseline grid set 14pt space, text frame with Arial 12pt and height of 3,8 mm. If you accidently move the text frame between the baseline grid lines the text vanishes. You can not see the reason why, until you deselect the text frame. When you deselect, the text frame has now the red indicators. Increase the height of the text frame and the text is visible again. Rare case but possible. -
Visible text disappears when pulled over Object
Joachim_L replied to DBerlin81's topic in V1 Bugs found on Windows
You had a text wrap set to the grey area, so the text jumped to the bottom of the page. Remove the text wrap for the grey area or set the Text frame to Ignore Text Wrap. P.S.: Forget what I said about Baseline Grid. -
Visible text disappears when pulled over Object
Joachim_L replied to DBerlin81's topic in V1 Bugs found on Windows
It seems to be, that you are using a baseline grid for the document and the content of the text frame might be set to align to baseline grid. Tell the text frame in Text frame panel to Ignore Baseline Grid. -
-
Seems to be a rendering problem only. Edited the file in APhoto and there is no jump in colour values.
-
My eyes are not the best anymore, but could it be, that there is some kind of halo when attaching gradients to an element? See attached image. I see this halo also in radial, elliptical etc. gradients. Second question: What is the opacity slider for? In my case I cannot move the slider. halogradient.afpub
-
@Lagarto This is weird. You picked those Pantone colours from list inside Publisher? I made myself a application wide palette with some colours including HKS 7 and some tone variants of it. Created a gradient from HKS 7 100% to HKS 7 28% and exported without any problem. Funny thing in your Publisher document is, that Pantone Blue does not appear in the PDF as colour, in fact even Rhodamine is ignored in the upper gradient. But Pantone works as spot colour. For testing I just added two squares with just Blue and Rhodamine.
-
Plugin-Support for Designer
Joachim_L replied to Joachim_L's topic in Feedback for Affinity Designer V1 on Desktop
In Affinity Photo we have support for third-party plugins, so I have the hope that plugins can be used one day in Affinity Designer. But I guess with plugin support for Affinity Photo a larger area of potential customers can be attracted. But there is a market for all those having e.g. a vinyl cutter and are forced to use either some weird applications or plugins. -
Place Randomly Changes to TXT Instead of All
Joachim_L replied to SilverSurfer1221's topic in V1 Bugs found on Windows
Ups, misread, wrong forum. Happens also with Publisher. I can confirm it happens in .471 from time to time. This seems to be never been fixed since the betas. -
Setting a shape with "NO STROKE" still leaves a space
Joachim_L replied to Shelbi's topic in V1 Bugs found on Windows
OK, understood well what you told. My doctor told me recently, that my ancestors were probable Vikings so I love to prolong the battle here. Question 1a,b,c,d (still not answered): What is a 0.000001 pixel or as Walt suggested a 0.001 pixel? Or how does it look like? Do I get it printed? Does it have an impact using it for web? Question 2: In which case we could need a pixel unit with 6 decimal places? Question 3: If we would agree that no decimal unit is needed for the unit pixels, so finally we would need no Force Pixel Alignment? My thinking is, that a lot of questions regarding blurry edges or thin lines will not occur if there were no decimal places for pixels. But in the end I can live with design decisions made, because all of you offered valid solutions to me. So thanks for that.- 22 replies
-
- no stroke leave space
- space between objects
- (and 2 more)
-
Setting a shape with "NO STROKE" still leaves a space
Joachim_L replied to Shelbi's topic in V1 Bugs found on Windows
@GabrielM I understand what you want to point out, but from my understanding this is causing these "pixel perfect matters". Argglll, I wish my English would be better to tell you my concerns, but I'll try. I will focus mainly on decimal places for pixels and manually creating objects. Lets say a user set decimal places for pixels to 0 and wants to align two objects of dimension 200x200 px side by side. This user could not do this by manually creating a square which is doable according to the information of the Transform panel. Best practice would be using only the Transform panel for creating / positioning the squares. Still I am not getting the sense in having decimal places for pixels. How does a 0.00005 pixel look like on a display? Aside from giving errors to the export. Hope I made my concerns clear enough?- 22 replies
-
- no stroke leave space
- space between objects
- (and 2 more)
-
There is a "bug" in the German help section. Posted this already in an other forum. The German help says Leinwand zuschneiden or Leinwandzuschnitt aufheben, whereas the menu items say Leinwand begrenzen und Leinwandbegrenzung aufheben.
-
I have to apologize. Reading help first in English I did not understand the real meaning of Clip Canvas. I should go to a refresh course for English. Anyway: The German help says Leinwand zuschneiden or Leinwandzuschnitt aufheben, whereas the menu items say Leinwand begrenzen und Leinwandbegrenzung aufheben.
-
Normally you get the image trimmed with Document -> Clip Canvas, when I understand the help document correctly. But in my case Clip Canvas and Unclip Canvas are both reverting the image to the original size. But when you export the image with the -2.3px overflow and open the image again the overflow is gone. Edit: Tried with an image that has a lot of transparent room around the main motif and Clip Canvas removed the transparent space. Nothing I would expect reading the help document.
