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

fde101

Members
  • Posts

    4,874
  • Joined

  • Last visited

Posts posted by fde101

  1. We log into the forums using an email address, meaning we all have one, making it the least common denominator for this functionality, and better than nothing.

    That said, email itself is not particularly secure, so I agree that other options are definitely preferable when available, where this is of significant concern.

    It is unrealistic to expect that many sites will support 3rd party authentication devices at this stage of the game, and SMS support is not always free to offer support for.

    While cell phone companies have traditionally allowed you to email a message that gets delivered as an SMS, many of them have started pulling back on support for this, and the address you send the messages to is formed differently for different people even on the same provider in some cases, making using these services challenging and somewhat hit-or-miss.

    Other SMS offerings are usually at a cost, which not all companies will want to pay when offering free accounts to a publicly accessible forum (meaning an unbounded number of SMS messages may need to be sent, thus a cost which is not controlled and which they may not be able to recoup).

    Offering support for signing in using a Google account appears to be free, and allows support for Google Authenticator if enabled for the account, so that is probably one of the more realistic options that many sites would be able to offer as an improvement over emailed codes.

  2. It appears to be Unicode character 1E3F: https://codepoints.net/U+1E3F?lang=en

     

    4 hours ago, BarbaraSki said:

    If you have any idea how to switch that off

    From the perspective of the Affinity software, it is not something you switch on and off.  The "m" with an accent (there are others in addition to this one) is a separate letter from the "m" without an accent - so if you have one and don't want the accent, you would replace it with an "m" that does not have an accent.

  3. 1 hour ago, mogsie said:

    For instance, search for what is NOT colour 0 0 0 100 CMYK so that I can make sure there is no lurking rich black

    Search for what is, then invert the selection.

     

    17 minutes ago, Old Bruce said:

    I honestly wish the Mac OS finder would allow me to search for things using Not.

    It does, but it is a bit more complex than it should be to get there:

    image.png.4a99aa8a1120080db630d48c0cde28c5.png

     

    1. Click the search button in the title bar and search for some random text 
    2. Click the "+" next to the "Save" button
    3. Option+click the "+" on the added iine (it turns into "..." while holding down option)
    4. Change "Any" to "None"
    5. Remove the line originally added in step 2
    6. Set your criteria in the area below "None"
    7. Clear the text of the original search
  4. 3 hours ago, GarryP said:

    And should the displayed aspect ratio be reversed, or not, when the document orientation changes between landscape and portrait?

    It is typically width : height, so a classic monitor or a 4/3 camera sensor size would have a 4:3 aspect ratio, typical TV resolutions such as HD and Ultra HD are 16:9, and DCI cinema formats such as 2K and 4K are 17:9, for starters.  If flipped to portrait, it would be 3:4, 9:16, 9:17, etc.

     

    3 hours ago, GarryP said:

    For facing-page documents in Publisher, should the displayed aspect ratio be for a single page or the whole spread?

    Even a facing pages document typically has single pages for the first and often last spread, so this one is a bit more up in the air.  My vote would be to stick with per page?

     

    3 hours ago, GarryP said:

    Should the displayed aspect ratio take bleed into account, or not?

    Bleed is not part of the page proper - it is an overprinting area to allow for cropping.  I would exclude it.

     

    3 hours ago, GarryP said:

    How many decimal places should be displayed when the numbers are not integers?

    Two is typical in the film/video world, which is where I suspect this request is probably coming from.

  5. Hi @luisduzzi, welcome to the forums!

    Yes, this has come up before.  I agree that having more options for these things would greatly expand the range of what is possible using the Appearance panel.

     

    Here is an example of a past thread requesting this:

     

     

    In general it is best to keep discussion of one request in one place rather than spread it out over multiple threads.

  6. I don't think exporting a Publisher document to a Word document would be practical.  Exporting the text of an individual story, sure, but not the entire document.  The structure of a DTP document is just too different from that of a traditional word processing document - it may be possible to export something which loosely resembles the Publisher document, but it would not be practical to work with in Word and some of the formatting would be very likely to break during the export.

     

    On 1/22/2024 at 2:52 PM, tzvi20 said:

    export the DOCX format as that I what my college wants

    Convince them that what they really want is PDF.  DOCX files make for a *very* poor distribution format, however much some people might wish to pretend otherwise.

  7. 14 hours ago, Bit Arts said:

    this very theoretical construct

    You might feel that way if you are accustomed to thinking of a traditional photo app, but one limitation of raster layers is that their data is directly editable (the very thing you are trying to accomplish) which means that their data must be stored within the document file itself.  They cannot be placed as linked - they must be embedded.

    There are numerous desktop publishing use cases where it would drive users just as crazy if this feature you are proposing ever became a default - there are reasons why they would want images to be linked rather than embedded, and image layers are essential to those workflows.

    I don't think this request would be a popular addition to Publisher, and for Designer it is marginal, but I do agree that a checkbox in Preferences/Settings for Photo to auto-rasterize newly placed images would make sense for some workflows, though caution should be applied before consideration of making it a default, as current versions of Photo also support linked placement, and would similarly need to use image layers if users choose to take advantage of that option.

     

    Another limitation of pixel layers is that they can only contain raster data.  Vector images can be placed and remain vector, so SVG files for example remain perfectly scalable as image layers, a property which would be lost when rasterizing to a pixel layer.

  8. Hi @Andres Flores, welcome to the forums!

    One challenge is that they would need a Vision Pro to test the software on to make sure it works, otherwise they will be getting support issues that they can't realistically address since they do not have the hardware.  Additionally, the Vision Pro seems to be designed for one person to use, so they may need multiple $3500 single-developer systems for what may in the end prove to be a niche product.

    It is not clear at this time how many of these will sell in its first iteration, so I can understand developers not wanting to jump the gun on pouring resources into supporting it until we see how it will fare in the market.

    Note also that these apps on the iPad primarily benefit from the precision of input using the Apple Pencil, and all indications are that much of this precision will be lost with the AVP and its advertised input methods - it will probably not be as easy to provide precise drawings on as even using a finger on an iPad - so the apps may not map well to the platform in the first place.

    This is a relatively new category of product so it is understandable that a lot of developers will hold back on supporting it initially.

  9. There is evidently a Blender plugin for sbsar files that relies on a component called Substace Automation Toolkit to be installed, but when that is available, is able to render sbsar files directly within Blender: https://xolotlstudio.gumroad.com/l/stxJi

    It might be possible to take a similar approach with the Affinity products to gain access to these files if it is something you have a use case for - if Serif does not provide this, perhaps as a plugin once the SDK is available?

  10. Bear in mind that even minor version updates to the Affinity apps break file compatibility.  If such an SDK were offered and a viewer app was built to support files from version 2.9 (picked at random), then as soon as 2.10 came out, you would need to choose between updating to 2.10 to take advantage of its improvements but losing support from the file viewer app until that app is updated with a newer SDK, or staying on Affinity 2.9, potentially losing compatibility with files from trading partners who *have* updated, until the viewer app is similarly updated.

    The one way around this is if the SDK uses components from the Affinity apps themselves, requiring them to be installed for the SDK to work - that would mean the viewer app could support displaying files from the Affinity apps only if at least one of the Affinity apps (of a compatible version) is installed on the system.  If the communication between the SDK and the app is reasonably stable between versions, that could allow compatibility with the same files as the installed Affinity app(s).

  11. 1 hour ago, Pyanepsion said:

    Subtitles are available in several languages

    Looks to me like they are available in any language you want as long as it is French.

     

    3 hours ago, loukash said:

    Is there anything wrong with the Smart Mode?

    Agreed, smart mode of the pen tool seems to do the same thing.  The key differences seem to be that in Illustrator you double-click for a straight line while you control+click (Mac version) in the Affinity products, and in the Affinity products you hold down the command key (Mac) to move a node.

  12. On 11/16/2022 at 7:19 PM, deeds said:

    Blender is an abomination. 

    I'm going to have to disagree on this one.  It is partly a matter of perspective.

    Blender does not conform to the user interface guidelines of practically anything - it is off in its own little world - so from that perspective, yes, it is a "foreign" piece of software no matter where you run it, with its own distinct learning curve and not quite fitting in with anything else.

    However, people did experiments in the past (before some of the sweeping improvements that have been made to the UI in more recent versions), and found that if they took someone experienced in Blender, and someone experienced in one of the commercial 3D apps, and had the Blender user and the other app user do the same thing (this was for modeling if I recall correctly), the Blender user could generally do it much faster.

    Blender's interface is not optimized for new users or to make it easier to learn (again, this has improved in the more recent versions, but it still is not the main focus).  Rather, it is optimized for speed of working after you learn it.  Someone who spends a lot of time working with Blender can become very fast in what they are doing - this is one of its primary benefits.

    Blender is an example of a true professional interface for people who heavily use the same app frequently.  It is not a good UI for people who use it sporadically or for people who want to walk up and just start using it (again, this is improving with the current versions, but is still not the main focus).

    When you look at it from that perspective, Blender is a program that people try to conform to a different mold than the one it is primarily intended for, them come away from it disappointed that it is not what they expected.  When you approach it for what it actually is, the interface is quite good.

    Of course, it is not completely perfect even within that category, as evidenced by the fact that they chose to base their scripting on the Python language.  Sad.

  13. If trying to flip a layer that covers the entire document area I'm also not sure how this would be useful, but consider a smaller layer which has some element which is visually aligned with something behind it at a specific vertical position.  If you want to flip that upper layer but keep it aligned, you would want to anchor the flip at the position which should remain aligned.

    Another example might be a shore line where you want to reflect a building into water which is below the line.  If you duplicate the content then flip it at the line this may sometimes give you a good starting point for positioning the reflection.

     

    One method of getting close to this is to resize around the transform point by dragging the appropriate top/bottom/side handle while holding down (command on the Mac); if you resize past the transform origin it will have the effect of flipping the layer, the catch being that you need to manually match the size to the original size and it may be slightly off.  For a reflection this is probably not much of an issue as you would likely wind up resizing it anyway after the flip and with this technique you can do both in one step... for other use cases how much of an issue it is will vary.

     

    I agree that having it flip around the transform origin when the origin is enabled would be a good idea, and I believe this has been requested before at least once or twice.

  14. 51 minutes ago, MikeTO said:

    I added this to my first post:

    Support multiple stories per page use case: When auto flowing a document page frame, if a single text frame exists on an existing page, AutoFlow will skip that page. This makes it impossible to use AutoFlow for both stories in a side-by-side layout (e.g., a Bible translation). AutoFlow could instead check if the new frame would overlap with an existing frame on the page. If it would overlap, create a new page, but if not, then create the frame on the existing page.

    This behavior would break if the frames were on a master page.

     

    Try this: in a new document, put two text frames on a master page.  

    Go to the document page and paste a large amount of text into each of the two frames.

    Auto-flow one of them.  You wind up with X number of pages, each with text in the frame you auto-flowed, and on each page a blank frame that came from the master.

    Thankfully, the existing feature is smart enough to link the frames when you auto-flow the other one - it does not create new pages as long as you do it right away without putting content in the intervening frames (if you do, then auto-flow creates new pages at that point instead of reusing the existing ones, which is understandable but also undesirable).

    Making this a property opens the possibility of having the frames pre-connected when any auto-flow activity takes place, which has the benefit of reducing the likelihood of a user accidentally putting something in one of the intermediate frames and disrupting a later auto-flow at that point.  It could also be pre-rigged and tested in a template.

  15. Why not make "autoflow" a property (checkbox) of the text frames?

    Not only would that solve this problem but it could also connect separate frames from the same page which are also set to autoflow so that if you have parallel stories which are independent of each other but which both span a shared set of pages (ex. a parallel bible where there are two different bible translations side by side in columns but each spanning the same set of pages) then both sets could be connected with themselves (but not each other) automatically as pages are added.

×
×
  • 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.