Jump to content
You must now use your email address to sign in [click for more info] ×

AdamStanislav

Members
  • Posts

    537
  • Joined

  • Last visited

Posts posted by AdamStanislav

  1. Yes, I was trying to create a preset for SVG. I named the preset Adam, and that was when the crash occurred. After restarting I noticed all default SVG presets were named SVG (xxxxx), so I tried again, this time naming it SVG (Adam). At that point it neither crashed nor created a new preset, so I gave up trying and just change it manually every time.

     

    The exact Export options I was trying to change, from the SVG (web) preset to a new preset, were having text converted to curves and having line breaks in the output.

     

    As for the crash when saving the file under a new name, it happened again this morning, but it does not happen every time. This time again, it crashed after it was done saving the file, so I was able to recover it. This is on Win 8.1.

  2. I think it's just a question of priorities. We will probably implement smart quotes as an 'Auto-correct' type feature which may well debut in Publisher, but could then subsequently be ported to the other apps. Until then you can use <Alt> codes or CharMap as outlined above.

     

    If you do, please make sure to keep it optional. And perhaps include a feature to protect specific non-smart quotes from being converted to smart quotes while still auto-converting others. After all, if you’re writing a book or an article on the proper use of quotes, you may need to use both types in the same book or article or illustration (graphic).

  3. I'd be interested to know whether either version can distinguish between Adam's nice 'Crusader' dingbats and an ordinary Latin text font, but I suspect not.

     

    My guess would be they can read the OS/2 table in my font (and other OpenType and TrueType fonts). It contains a key called PFM Family whose value is set to Decorative (other possible values are Serif, Sans-Serif, Monospace and Script). I’m not sure how easy it is to get this information on either OS but, at least in theory, it should be available.

     

    BTW, thanks for calling it nice.  :)

  4. Okay, so RAW data is the default picture quality from the right kind of digital camera, and users were concerned that the program wasn't able to read this quality?

     

    Absolutely! I disagree with the comparison of raw to an undeveloped negative and jpeg to the fully processed photograph, at least not as they come out of the camera. Jpeg is a lossy compression format. That means it throws away some of the image data. Actually, it throws away a lot of it based on the (questionable, imho) assumption that the untrained eye (which in itself is a silly expression, it is the brain that may or may not be trained, not the eye) won’t see any difference.

     

    And in the camera you have no control over what data it throws away. It is fine for vacation photographers who perhaps really cannot tell the difference anyway, or simply don’t know their camera may be capable of giving them much more. It is, however, completely unacceptable for professional photographers who want to have complete control over their pictures.

     

    Raw is what the camera sees. It is uncompressed and unedited. It is huge, too. It is the difference between a Rolls Royce and a Chevy. Personally, I have my camera configured to give me both, raw and jpeg, of each picture. And I decide whether the jpeg will do for whatever I am doing or whether I need to work with the raw data and, only after editing it, create a jpeg to deliver to others.

  5. If using the node tool, just click on one. Then hit delete. While the bug is still there as regards things moving, in this case it doesn't matter as it is being deleted.

     

    The above works fine here.

     

    I actually tried that after my last post. The problem was that clicking on one did not necessarily pick the one I wanted to delete (the one that was not smooth). I had to try clicking and shift clicking over and over, also watching for any moves (and ^Z to undo them) before it selected the one I wanted to delete.

     

    Eventually I got it done, but we really need an easier way to select the node we want to select!

     

    On a related topic, once a node is selected, we are able to move the node by typing in a new X and Y, or even move a group of them by using the nice feature of -=20 and +=20. But, unless I’m missing something, we have no way of typing in the exact values for the control points of the curve. I tried dragging around the control point in the hope of selecting it and getting its coordinates in the coordinate boxes, but the moment I pressed the mouse key the control points disappeared from the view.  :huh:  I wish when a node is selected we could type in not just its new coordinates but those of both of its control points (assuming one or both sides of it are not connected to a straight line).

  6. Here is the file it happened with.

     

    Cross-58.afdesign

     

    Upon closer examination, I noticed there are two nodes overlapping, one is smooth, one is not. I have no idea why AD decided to put two nodes in there. IIRC, all I did was doing was using the corner tool a lot along with baking the corners.

     

    I really wish we had the simplify tool in AD as we did in DrawPlus, and in just about any other vector editor.

  7. To me the major problem with the font list is that it only shows the names of the fonts in the fonts themselves, so you cannot see the names of fonts that place dingbats or other graphics in place of letters, as in this capture:

     

    post-32179-0-36403100-1473528820_thumb.png

     

    It would make more sense to display the name of each font in the regular system font followed by same in the font itself. That way we could both read the names of the fonts and see what they look like.

  8. Yes, thank you, they were very useful, as were many other tools.

     

    For example, the shape assigned to the letter P started off as a simple square. I then placed a large vertically centered circle to the left of the center of the square. I duplicated the circle and placed the duplicate same distance to the right of the center. I selected all three shapes and had AD subtract the circles from the square. That gave me the vertical beam of the design. All I had to do next was duplicate the vertical beam, rotate it 90° and add the result to the vertical beam.

     

    The shape assigned to the letter e used the same technique, except I started with a circle instead of a square.

     

    It took me a while to figure out how to create the shape assigned to the letter T. It finally occurred to me that I had to start with two partially overlapping vertically aligned circles, add them to one path and then continue with the same technique mentioned above.

     

    AD makes it all so simple!

  9. AD will create bitmaps all too easily even when there shouldn't be any in the PDF, and so I have had to try multiple settings in exporting PDFs. Silly.

     

    Not just in PDF. AD will create bitmaps all too easily in SVG exports even when it could be using SVG filters. That is why I never use AD’s own effects, but export to SVG and apply effects in Inkscape or by directly coding them in SVG.

  10. I'm sorry to say I'm having a hard time attaching it. If I type %APPDATA% into the search, I am brought into the AppData and then Roaming folder, where I can later find the crash reports. However, if I try to add an attachment and search from scratch, the AppData and Roaming folders don't seem to exist, even if I look in the folder before them.

     

    That’s because they’re marked as hidden, so they do not appear in a standard listing. You need to type the directory into that narrow window above the list of files, where the current directory is listed, and it will switch there (assuming you’re logged in as an administrator, which, unfortunately, most Windows users are at all times).

  11. I don't think it would be due to memory as Adam mentioned.

     

    I mentioned an invalid pointer. That means the software tried to write to an invalid place in the memory. That has nothing to do with how much memory you have installed or how much memory is in use. An invalid pointer is probably the most common programming error, and also one hard to catch since it can be just about anywhere in the code.

     

    Anyway, see it right from the horse’s mouth that 0x80004003 = E_POINTER (Pointer that is not valid), at least under Microsoft Windows.

     

    As for your question what you can do about it, unfortunately nothing (other than reporting it, which you already have). The AD software developers need to find where the error occurs and fix it. I should point out (to them) that this is a new error that was not present in prior Betas, so it should be somewhere in the code new to this Beta.

×
×
  • Create New...

Important Information

Terms of Use | 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.