-
Posts
205 -
Joined
-
Last visited
Reputation Activity
-
matt.baker got a reaction from Chris B in Font autocomplete/filter
Thanks Chris. Good idea.
I've never tried safe mode with an account that requires a domain login (no local account access at work), but hopefully safe mode with networking should do the trick. If that works I'll try disabling startup services and programs logically to narrow down the conflicting one.
-
matt.baker reacted to scamper in Hide shape handles whilst applying Layer Effects
If I draw or select a shape, its handles and bounding box are active as long as it's selected. Okay so far. But when I elect to add a Layer Effect, the handles and bounding box should be temporarily hidden, as they can obscure the very effects I'm carefully applying.
I realize that, unlike Photoshop, AD allows me to edit/deselect a shape even while the Layer Effects window is in the foreground. It's not really a modal window! So what's the solution? Well, a compromise might be to hide the handles and bounding box, when the Layer Effects window is present, unless my cursor explicitly moves over the active shape -- making those things more sensitive to my actual intent, in other words. Otherwise assume that I need those to be hidden until I've dismissed the Layer Effects window.
-
matt.baker reacted to Chris B in Font autocomplete/filter
Ah I remember that post. Jon and myself couldn't reproduce it at all :angry: We do come across unique issues from time to time. Some of them can be caused by other software running in the background. You could easily identify that by booting in Safe Mode so the only things running are your necessary Windows processes and whatever else you choose, such as Designer. If you haven't booted into Safe Mode before I'd definitely look it up so you're comfortable with what you are doing.
-
matt.baker reacted to Mark Ingram in Crosshair cursor on dark backgrounds
OK, I've just checked the cursors for these tools, and the white outline isn't actually white! At 100%, it's only 30% opaque, and at 200% it's 60% opaque! I'll see about getting these changed to improve visibility.
-
matt.baker got a reaction from Mark Ingram in Font autocomplete/filter
Arghhh, It would appear that it is my work PC (again) causing similar effects to this: https://forum.affinity.serif.com/index.php?/topic/26570-15025-rc-colour-numeric-fields-buggy-after-enter-key/
Sorry, please ignore this bug (unless you have any ideas on what could be causing it on my machine/ logs that may be of use?).
I just got another PC running Windows 10 Pro
set up at work today, so I'll also try it on that when I'm back. All my other test PCs where it works have been Win 10 Home Premium.
Thanks
-
matt.baker reacted to Chris B in Crosshair cursor on dark backgrounds
Hi mattb5906,
This has been mentioned a few times. Can you try adjusting your sliders from Preferences > User Interface to see if that helps.
I'm sure I saw one of the developers was going to take a look at this. On the Mac, the lines of the crosshair are denser so it is more visible.
Thanks
-
matt.baker reacted to Chris B in Font autocomplete/filter
Hey mattb5906,
We are aware of the paragraph panel not displaying correctly however I would expect to be able to search for more than 1 character in a font. It works on the Mac. I'll get this logged as I can't see it in our bug reports.
Cheers :)
-
matt.baker reacted to Mark Ingram in The launch-time of AD needs more time than Illustrator
I've just done some analysis on our startup time, and I can see some areas which could be improved. I might not have time to fix them before release, but I will do it at some point. In theory it should make it over twice as fast to start up...
-
matt.baker got a reaction from StufePOETS in SVG Export - Unnecessary g transforms
Why does Affinity insert unnecessary transforms when exporting as SVG?
With the example document, the SVG export gives:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 12 11" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:1.41421;"> <g transform="matrix(0.8,0,0,0.916667,-446.4,-374)"> <rect x="558" y="408" width="15" height="12" style="fill:rgb(235,235,235);"/> </g> <g transform="matrix(1,0,0,1,-561,-409)"> <path d="M567,411.501L569.499,416.499L564.501,416.499L567,411.501Z" style="fill:rgb(153,153,153);"/> </g> </svg> This can be simplified to:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!DOCTYPE svg PUBLIC "-//W3C//DTD SVG 1.1//EN" "http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd"> <svg width="100%" height="100%" viewBox="0 0 12 11" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xml:space="preserve" style="fill-rule:evenodd;clip-rule:evenodd;stroke-linejoin:round;stroke-miterlimit:1.41421;"> <rect x="0" y="0" width="12" height="11" style="fill:rgb(235,235,235);"/> <path d="M6,2.501L8.499,7.499L3.501,7.499L6,2.501Z" style="fill:rgb(153,153,153);"/> </svg> The original seems an overly complicated way of doing it.Up arrow.afdesign
Up arrow Affinity.svg
Up arrow Modified.svg
-
matt.baker got a reaction from Mark Ingram in Install latest Beta problem
Odd that a reboot of the machine didn't clear those.
-
matt.baker reacted to ronnyb in Easter Egg
Definitely not a high priority (well maybe)... Would be cool to have the viewport "go quantum" when one reaches the limits of the virtually infinite zoom... like the "noise" made on a tv set to no channel, or static.... :ph34r:
-
matt.baker reacted to Sean P in Transform pin position / relative tool
Hi Matt,
This is actually as intended. The white square shows you the top left position of the object making it easier to track it's orientation and position when it has been rotated. The selected anchor point however will appear larger (seen in the centre of your 'Actual' screenshot).
-
matt.baker reacted to Mitschel68 in improve document properties with meta data
Hi,
I'm using AD now for a while and I'm highly impressed of the possibilities. The main goal is to generate marketing material for our company, which results in PDF files (brochures, product information sheets, ...).
I see a bigger improvement with the meta data AD is generating, because there is no influence on the title, author and so on. For instance: The title in the meta data of the PDF is the full path incl. the file name. This is not needed.
For tagging the PDF's for SEO it is hardly needed to be able to add some meta data right in the document properties.
Of course you can edit the tags afterwards, but to have it at one place would be better for my personal workflow.
Would be nice, if you take this into account. Thanks a lot.
Regards,
Mitschel68 (Germany)
-
matt.baker reacted to BatteriesInc in Meta data facilities for export (author, copyright etc)
Hi,
As you are no doubt beavering away at making Affinity products even better (and I can't wait to hear of any update on any DAM and DTP products, hint ;) ;) ), maybe it's time to throw this into the mix: meta data handling.
Especially those that work commercially need to make sure their meta data is set correctly as that often influences how the work is archived, retrieved, distributed and sold.
This means different things in different formats (in PNG and JPG it would be stored in PCT/EXIF tags, but PDF has quite a few fields too), but there are some common themes: artist/author, copyright holder and maybe distribution. Where possible a freeform field would be good where the meta format allows, because you could use that for library markings (which could help with a DAM retrieval mode, for instance).
To use this, you'd need facilities to set and edit these fields, and a way to template an optional default. At present there's nothing for that in the AD/AP export facilities so you end up having to reprint/edit PDFs and run the venerable exiftool over images to add the data.
Cheers!
PS: I'll be in London next week - if any of you guys venture into town I'll buy you a beer :P
-
matt.baker reacted to bellyanalytical in Document user variables
Ah,
aha -
ok - i only found the popup when you click on the button in the red circle: "path component" in english. the screenshot above refers to the popup related to the button in the green circle - that one is new to me.
well, basically i understand what you can do there - for example:
i was putting a path description into the path component " ./subfolder/" which automatically exported that slice in that "subfolder" in the export folder.
then you can also add "variables" which modify that path - or filename. for example the "slicename" variable will output the name of the slice. you could do:
"/weirdexports/[slicename]/" - and your exports will be put in a subfolder "weirdexports/slice1" ...
in the other popup you can modify the filename in the same manner.
(@mattb5906)
and I just found out that you just have to click or doubleclick right below "name" in the list to be able to add your own variable. there you can enter a name - and on the right side a value.
you are able to reuse snippets then ... (i guess in all documents)
but ---- !
I'd like to see more variables.
For example, I don't like it to navigate to the correct export folder every single time again when I am editing another document. There could be a variable "document root" which will contain the path to the document.
so you can setup a neat export ..... setup ...
mh.
-
matt.baker got a reaction from KarlenSpix in Document user variables
On the export options for slices I see a 'User variables' section. How can I make use of this?
Thanks
-
matt.baker reacted to Jon W in Preferences are not cancellable
Actually the changes are applied instantly. It's a modeless dialog, which means you can leave it open while you do other things. This type of dialog never has a cancel button.
-
matt.baker reacted to Chris B in Preferences are not cancellable
Jon makes a valid point. I apologise for not realising it was modeless. I hope this makes sense mattb5906.
-
matt.baker reacted to Chris B in Preferences are not cancellable
Hey mattb5906,
I actually think having a 'Cancel' or 'Reset' button would be a good idea. I suppose it makes perfect sense to be able to cancel any changes, especially if you can't remember what changes you made. I can put this forward as an improvement.
As for the Preferences not saving, I'm pretty sure we have this logged already. If it isn't, I'll make sure it does get logged.
Cheers! :)
-
matt.baker reacted to Chris_K in [1.5.0.14] UI sliders still buggy
Thanks mattb5906
I'm getting this too so I've re-opened the issue in our database
Thanks
-
matt.baker got a reaction from fapedMum in [1.5.0.14] UI sliders still buggy
The UI colour sliders are still buggy in the user preferences. As soon as the UI gamma slider is adjusted, the top two sliders become unresponsive and only change to the new positions once UI gamma is changed again or the user preferences are closed and reopened.
The UI gamma slider is also jumpy (lots of processing?) when moving.
-
matt.baker reacted to Chris_K in EMF export - More options crash
Hi mattb5906
I've managed to recreate this quite easily so I shall get it logged
Cheers
-
matt.baker reacted to Alfred in Gradient tool - Unselectable nodes
Since it does work, I suppose it could be argued that there's no bug, but there's certainly room for improvement!
-
matt.baker reacted to matt.baker in EMF exports with extra white space
I'm unsure whether this is a bug with Affinity or a limitation with the EMF file format, but when exporting the attached document as an EMF extra white space is added to the right and bottom edges. I have verified the white space is present in 4 different applications (Microsoft Office, LabVIEW, Inkscape and an online converter to PNG) so I'm assuming they are correctly rendering EMFs. I've tried changing the resolution to 96 dpi instead of 72, but the same thing happens. It seems to be only certain paths/sizes.
If the ascpect ratio of the original are 1:1 it works correctly, but if it's say 100x75, it's most noticeable.
If I open the EMF in Affinity, it renders without the extra white space.
If I open it using the Microsoft Office 2010 image viewer, it reports the size as 11x10px even though the Affinity document is 12x11px.
A similar thing happens if the original image is larger.
It's almost as though Affinity is exporting partial pixels (rounding error?).
Inkscape has now decided not to render the EMFs (displays as a white document) so I'm unable to provide a screen shot of that case.
Not permitted to upload an EMF, so here's a link: https://www.dropbox.com/s/pin3a6wo7nesypv/Up%20arrow%20Affinity.emf?dl=1
More test files at 72dpi:
https://www.dropbox.com/s/z2cajl6vf7mxj41/100x75.emf?dl=1
https://www.dropbox.com/s/hm6fu25nt6dxnji/100x100.emf?dl=1
https://www.dropbox.com/s/yiagm82oqj9332o/100x120.emf?dl=1
Up arrow.afdesign
-
matt.baker reacted to Alfred in Gradient tool - Unselectable nodes
As you have hinted in your screenshot, pressing the 'Reverse' button makes the blue node selectable on the left, so you can delete it and then simply reverse the gradient again.