PaoloT

If you place an image inline that is larger than the text frame, you will overflow the entire story.
I'll use an example of a long book with frames of equal size. If I place inline an image that is larger than the current frame, Publisher will move to frame +1. If it doesn't fit there, it will move to frame +2, etc. Finally it will overflow the final frame in the story.
But I'm still on page 17 and the image didn't appear, and all the text below the cursor has disappeared. I have to scroll to the end of the story on page 53 where I can click the show overflow icon to see the image. Only then can I scale the image so that it fits in the frame. When I let go of the size handle the image disappears because now it's back on page 17 so then I have to scroll back to find it.
I think it would be better when placing an inline image to scale it to fit the current frame if it doesn't fit that frame or any future one in the story. This would leave the user with something they can deal with and they won't have to hunt for the hidden picture.
This happens to me regularly with my current project which has large inline images in narrow frames. I'm posting this here because I know it's an enhancement request, but to the user it really feels like a bug.
Thanks

The deal has fallen through: the planned takeover of the web design platform Figma by the software company Adobe will not take place. The reason for this: the concerns of the EU Commission and the British competition authority CMA. Takeover canceled: Adobe is not buying the web design platform Figma after all.

Every time I export slices, the app opens a dialog and asks me to select a folder where the exported files will be placed. This is very irritating and not very productive.
Therefore, I am asking you to add an option where we can set the default path to the folder where exported files will be placed, so that the application will not ask us to select the folder every time.
Similar to the "Export To" option in the "Export for Screens" panel in Illustrator.
 

Unfortunately, this feature seems to be conceived for mostly-graphical documents, not text-based ones. The ability to hide portions of text in the same layer/frame is not there.
Yet, it seems to me that it would make much sense in Publisher.
Paolo
 

Agreed. On Mac, the top window bar with the "traffic lights" buttons should never fully disappear. In some apps on current MacOS where a window looks borderless, the top window bar at least appears on hover.

@walt.farrell and @Dan C,
Found it. 
1. Hide the UI while a document is open.
2. You may close it or leave it open.
3. Create or open a document.
4. The new document is open in a window with the hidden UI, and no status bar is shown.

publisher-no-ui.mov    

Thanks for your report - I can confirm I've been able to replicate this here on macOS and I'm getting it logged with our team now
I'm also separately logging the platform difference between Windows and macOS, as when 'Toggling UI', macOS retains the Status Bar and Windows does not - though this might be an intentional decision.
I hope this helps!

Ok, but those are also those boring parts for which we wouldn't want to pay for! 😁
Paolo
 

Uh, now I got your joke. You've edited your post after I've already quoted it…  

What do you need the Tab key for, when you have the Spacebar to align your text??? 😁
 

I've not tried it recently. Not with the current beta, no.
Paolo
 

Are you perhaps experiencing the situation where you hid the UI, and then rather than restoring it (Tab again), you brought parts of it back piecemeal using the View menu? You can restore everything except the Status Bar that way. The Status Bar only hides or shows by hiding/restoring the UI using View > Toggle UI (or Tab).

Ah, good catch. Yes, that smells like a bug.
This fix is easy though: simply temporarily show and hide the UI, and the status bar will stay.

Seems to work OK for me, at least on Windows. Can you provide more details?

20240112-1856-21.7607381.mp4    

On Mac, one can: Use the status bar at the bottom!

Only, I can't seem to see a status bar when the UI is hidden.
But it's a bug. This seems to happen when you open a document with the UI already hidden.
I'm sure it also happened when I explicitly hid the UI, but can't reproduce it.
 
Sure, here it is! No status bar on sight!
If I make the UI reappear, and then hide it again, the status bar is there again. At least, this time.

At first I thought your observation made perfect sense, but upon reflection, I do think there is a need for both buttons, and that is because the visible state of the different objects that make up a query could have their visibility changed from the layer panel. For example, let’s say that you have some objects matching a state query that are currently invisible, and some others matching the same query that are currently visible. In that case with mixed visibility, which state should a single toggle show? In the current implementation, the two buttons are effectively “make all visible” and “make all hidden,” and they will both have an effect when the objects have mixed visibility settings.

I'd like to test changing words/terms within a larger portion of copy based on selected state.
How would I do this without duplicating the entire text frame, which is also connected to a flow of further text frames, if visibility is decided only on the level of layers?

Apps: All
Platforms: Windows, macOS and iPad
We have now added the ability to lock all insertion targets (Behind, On Top and Inside) in all apps. This is activated by holding Alt when pressing either of those buttons in the toolbar. This is particularly useful for those who like working from top to bottom in the layer stack, meaning you can now lock Insert Behind on so all new objects you create are inserted below the current selection.
The insertion target buttons are available in the top toolbar on Windows and macOS:

And can be found in the edit menu on iPad as shown below. On iPad you can lock these either by holding Alt when you tap on the appropriate option (from command controller or attached keyboard), or alternatively by long pressing on the button.

Is there a need for both the show and hide icons, would one togglable icon not suffice in the same way it does for Password Protection in the PDF Export settings to either show or hide the password? This would make it much easier to determine the state of any Query especially as currently there is no visual feedback in the States Panel to indicate when a Query is shown or hidden (other than looking at the canvas itself)...
Perhaps white icons in dark mode and dark grey in light move for consistency and simple ease of viewing...

A definite need, again as mentioned earlier in the thread, to be able to rename Queries...

I think we have exchanged some thoughts earlier about degree of usefulness of IDML serving as a kind of an exchange format between different layout apps (considering how it is currently implemented e.g. in QXP and VivaDesigner), but I certainly agree with you that these kinds of "incompatibility" concerns are silly.
IMO, speculations of "proprietary" or "nondisclosure" issues related to IDML are equally nonsensical. I am not sure how Adobe handles downgrading of features so that "new", post CS4-features get at some level included, but I have understood that IDML specs basically do not get upgraded because the idea is that layouts saved in IDML format, including ones saved in latest CC versions, can be opened also in CS4. If something is not "understood" by earlier versions, it is just skipped/ignored, .
As for reasons of current non-availability of (over a decade old) IDML specs on Adobe dev network (while IDML tools and cookbook are still available), we can only make guesses, but anyone googling IDML File Format specs gets the needed documentation as second and third find entry on Github and CreativePro (not particularly dark internet)... IDML file format itself is nothing more than zipped XML = plain text, so anybody can see how ID features are expressed in mark up. If Serif can convert that to native Affinity objects there is nothing in the technology that stops them doing it in the other direction. 

Adobe InDesign has the option save as IDML, a format which can be opened in earlier versions of Adobe InDesign and also in Affinity Publisher to be fully edited there as nothing happened – which is nice! What's the option the other way around – to save as this format also from Affinity Publisher so it's possible to open that file for edits right on also in Adobe InDesign?

Unfortunately we don't offer an export option to such a file format at this time, which is why we recommend PDF for transferring Affinity files to other apps.
This has been discussed in multiple threads throughout the forums previously, I'd recommend checking out one of the threads below -
You can find even more similar threads through a related Google search - 
https://www.google.com/search?q=site%3Aforum.affinity.serif.com+Publisher+to+InDesign
I hope this clears things up!

Yes agreed - I noted briefly on the post but we do intend to add the ability to save presets in a future update (but that will be after 2.4 release). Also to set up more complex rules based on multiple queries (e.g. in the example I gave in the OP you could set up a smart state which says "Turn all layers which fulfils EN query on AND turn all layers which fulfil DE query off AND turn all layers which fulfil JA query off". i.e. so in a single click you could get to your English version.

Apps: All
Platforms: macOS, Windows and iPad
Previously when you cycled your selection box this was only a temporary operation. You can now make this permanent...
From the select menu there are two options:
- Cycle selection box (this was the existing option)
- Set selection box (the new option)

Also note the shortcut for these - [Full Stop] to cycle and [CMD + Full Stop] to set on macOS and iPad or [Ctrl + Full Stop] to set on Windows.
The new feature is that after cycling to the selection box you want you can now permanently set that for your current selection by using the Set Selection Box command.
In the example below, I have two shapes which are rotated by the same amount. Therefore when they are selected by default the selection box is oriented to match the shape's rotation. Now if I want to permanently make those shapes have a selection box which is oriented to my page I can cycle to regular bounds and then Set Selection Box, which will now make that persist every time I select those items in future.

 
A couple of other notes on this feature:
As well as cycling to the base box and regular bounds of an object, if you have a grid set which has a different rotation to your page (or, are working on an isometric plane for example) you will additionally get the option to cycle and set the selection box to be aligned with the the current planar bounds of the selection. If you have a multiple selection which includes objects rotated by different amounts, if you wish to set your selection box for all objects in your selection to match the orientation of one of them you can set the one you want to match to be your key object. Then when you cycle your selection box the "base box" option will match that object's rotation.