Jump to content

CaptNeo

Members
  • Content Count

    28
  • Joined

  • Last visited

Everything posted by CaptNeo

  1. Hello, it would be really awesome if AD could add a simple, generic Batch Builder that can export coordinates for Artboards and Slices and basic information for exported object layers to either JSON or XML: Any slice Coordinates Slices created from objects Stroke: Thickness, Color & Alignment Fill: Color Slices created from text frames (assuming a constant style for the entire frame) Family Weight Size Alignment Bonus points for any additional properties (everything in the contextual context toolbar and the effects panel may be of interest) That would dramatically increase the usefulness for UI design in collaboration with development teams! We're currently trying to use the Spine JSON-Export to automatically create design specs for our dev team, but the proprietary structure (origin in bottom left, anchor at center of any object, no text support) makes it kind of finicky. It's awesome that it's there, but a few more attributes would make it much more useful for us. If it's too time intensive to make a pretty JSON/XML-file, I'd also settle for Batch Builder that prints a parsable ToString()-Dump of the document tree .
  2. Hi, attached you find the fonts and a snippet of the assets file. Install the 2014 version of Open Sans, and it renders correctly. Install Open Sans from 2018 and it renders as Arial, although the contextual toolbar displays "Open Sans" anyway. Thank you and best regards, Chris Debug Assets (Open Sans).afassets Open Sans 2018.zip Open Sans 2014.zip P.S.: Both machines run Windows 7, 64 Bit
  3. Hi, today I found, that there exist slightly different files for Open Sans v1.10. On one machine I've been working with a version obtained in April 2014 from Google Fonts (OpenSans-Regular.ttf, v1.10, 217360 bytes) and created an Assets Library that I shared with a colleague. That co-worker installed a recent Version from Google Fonts, and her OpenSans-Regular.ttf is also v1.10, but 217276 bytes, i.e. 84 bytes smaller. Now, AD won't render the assets correctly and substitutes the "missing" Font with Arial. I believe in this and similar cases AD should either automatically fall back on the identically named available font or ask the user for a substitution rule (like when opening PDFs). Regards, Chris
  4. I'd like to second this. This is quite essential for creating all sorts of precision shapes. Since everything else snaps wonderfully, I actually thought this was a bug. Ergo: Pretty please!
  5. Hi, I often work from home. When I do, I let my labtop hibernate, take it with me, and resume working using VPN from home. Problem is: Affinity detects that file handles are no longer identical to the ones before switching networks, and the error handling is quite punishing: The application behaves exactly as the message suggests: The unsaved document is being closed, even if it is still in memory and the path to the file is still valid. All changes since last (auto-)save lost. I know that my use-case is probably rare, but the error handling here is not ideal. At least let me save the document to a local drive and don't close it, while it is still safe and sound in memory. Regards, Chris
  6. I second this request. Makes it easier to use documents as templates.
  7. Hi, the constraint group feature is immensely awesome and helpful. However, I've encountered several problems, where the feature does not work as I'd expect. Here I'd like to document one such bug. It starts with a 320x320 constraint group which holds four containers: Yellow and blue are fixed-height headers and footers, that stretch with the parent Green and red stretch to fill the vertical gap between header and footer and their width will always be 25% of the parent So far, so good. Now, I'd like to start adding further elements to the four docked regions. Let's start with centered labels: The labels are Frame Texts without any constraints. Now, when I start to group each docked rectangle with its respective label, this happens: The nested groups do not "wrap" their contents as intended. Actually, the right and bottom groups don't even overlap the geometry of their children at all. However, the grouped items are still in the right place. Only the newly created "container" groups have the wrong dimensions. But here's the interesting part: When I scale the parent to match the 1280x720 artboard size, the dimensions of the nested groups almost align with the original 320x320 parent: Long story short: I believe, the dimensions of the nested groups are not computed in the right coordinate system. Somehow, the transformation from "global Artboard space" to "local 1rst-order constraint group space" is performed twice for the newly created "2nd-order" constraint groups. Regards, Chris
  8. That's your happy Valentine's gift from MS! Kidding aside, you had an impressive turnaround time for catching and fixing the issue after Chris J found the steps to reproduce. Chapeau! Doodled on the Surface for an hour or so, and everything still works smoothly.
  9. Awesome, and many thanks for hunting the bugger down! Will start playing with it immediately.
  10. In the mean time I managed to spend an evening with the Surface and Expression Design.During two hours of constant dooling and brush-switching I didn't experience any problems with the drop-down menus there.
  11. Wow, that's mighty impressive! You guys are doing an excellent job there. Back to the problem at hand, I'd bet Photoshop and ArtRage are running on older frameworks. Photoshop, because... well, it's Photoshop, and ArtRage has many fundamental scaling issues on hdpi displays that are not typical for WPF. Also, the Office-Team did not adopt WPF as framework (at least until 2013), so OneNote is off the hook as well. I'll try to replicate the bug with the Beta of Designer. Do you know by any chance, if MS Expression Designer uses WPF as framework? I believe, it does. I'd give it a try as well to see if the bug manifests there as well.
  12. Usually I don't do too much penwork with Designer, so I cannot speak to it (will try to confirm though, if that's helpful). However, I've worked for hours with OneNote, ArtRage 4 and Photoshop CC on the Surface. This specific bug does not occur in these apps, at least not so soon. What's your UI framework? I'd guess Qt QML because of the cross-plattform availability. Maybe one should try and test other apps that share that framework.
  13. Sorry to report that the problem occured in beta 1.6.1.93 after roughly an hour, while I was adjusting settings in the brush dialog.
  14. Thanks a lot, will download and setup immediately. Are there any logs/reports I should save and post if/when the problem resurfaces?
  15. Just reproduced it in Photo 1.6 (took 2-3h, though). Type-cover was attached, but with the cover on the back. Menus open, but neither pen or touch can trigger menu items. Pen and eraser still work on the canvas, though. Attached the type-cover the right way and could save my work using the trackpad While the unresponsive 1.6 Photo was still open, I started Designer 1.5 and there everything works just fine
  16. Very much like what I was experiencing, too. However, I also could not click buttons in dialogs.
  17. Yes, sure. Like sarahgould, I just need to restart the Affinity app to get going again. Windows and other apps work just fine.
  18. Hi Mark, has the dev team made any progress on the issue, yet? I've doodled a bit on my surface, and the UI is still responsive after 20 min. Was this addressed? I can't seem to find full release notes.
  19. I can also confirm that 15 min seems to be about right before the unresponsiveness sets in. Restarting the app makes it responsive again.
  20. Yes, according to "Settings -> Windows Update" it is.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. 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.