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

Gabe

Staff
  • Posts

    10,195
  • Joined

Posts posted by Gabe

  1. 1 hour ago, Hangman said:

    Is there a complete list of all the Payload structure options available for QR Codes, e.g., email, MMS, vCard etc., or is it restricted to URL, SMS, GEO Location and WIFI?

    URI schemes are not QR code specific. The QR code just makes them "readable". It's up to whatever app/tool reads the QR code to handle the URI.

    The official registered ones are available here > https://www.iana.org/assignments/uri-schemes/uri-schemes.xhtml, but I'm sure there are many other unofficial ones. 

  2. On 1/13/2024 at 5:14 PM, anto said:

    If this help.

    I did nothing and let the computer sleep again. External monitor turned off at the same time. I use a KVM-switch to switch between different computers.

    When I turned it back on, the window dropped down so that I could see it from above. But it looks like the size of the external monitor was remembered.

     

     

    I'm not quite sure what the video is trying to describe as it's not showing the entire screen. 

  3. 43 minutes ago, Dario said:

    Thanks for this awesome feature! Fits perfectly with my workflow. One issue that I noticed (Affinity Designer 2.4 beta on Windows):

    When I set the filename (Document name) variable in a new and unsaved document, save the document (to give it a name) and than export my slice, the name of the exported file does not contain the filename.

    Also if I have set up a document with the filename variable, then use Save As with a new document name and export my slice, the slices filename is not updated with the new document name.

    The same applies to the path if the filename variable is used there. Closing and reopening the document resolves the issue.

    Welcome to the forums.

    Thanks.We are already aware of this issue.

  4. This has always been the case for beta versions that are ahead of the retail (right now 2.4.x beta, 2.3.x retail). It happens whenever we add new features or change core functions, so you might find that once 2.4 is out for retail, a subsequent 2.4 beta will not be backward compatible. 

    44 minutes ago, mthorner said:

    How long are my beta-edits incompatible with you regular product?

    Essentially, until we release 2.4 retail. 

  5. 5 hours ago, Benfischer said:

    Seems to work OK, but with regard to Ash's description, the button that probably should be labeled Add New Query in the tool tip is actually labeled "Add New Smart State"image.png.535fae98e3f61bfdf3c305fc1ea6d76c.png

    The follow up windows for name and so on reference Query, as in Ash's description.

    MacOS, fwiw

    Are you using English US? If so, it's just a "translation" issue. Not all labels have gone through the translation process yet (even though they mainly the same for English US, they still go through a different process)

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