bbrother

I've been using APub (Affinity Publisher) for a few years now and haven't gotten around to this concept where paragraph and character styles are throwed into one bag. And I really tried not to be prejudiced against this solution and to give it a chance. This simply doesn't work and is not very convenient. And I really tried not to be prejudiced against this solution and to give it a chance. This simply doesn't work and is not very convenient. In addition to all this, there is forced sorting by name alphabetically. It's not good to work like this, especially in bigger projects.

@jaxfh, As for the floating panel for alignment operations, such a request has already been made. So you can share your opinion on this subject in the post linked below.

I agree @mikeTO. The changes in version 2.5, as you can see in the attached screenshot you attached, are a step back in terms of usability and appearance versus 2.4. This must be changed. It cannot be that some of the control elements are too wide and some are too narrow, causing the names to be truncated.

I'm not sure, and I don't think this is exclusive to beta 2.5, but if you've started making UI changes and dealing with inconsistencies, I'd like to draw your attention to the fact that the shape of the active tab in panel groups is different between macOS and Windows. In macOS (first from the left in the screenshot) it has a rectangular shape, while in Windows (second from the left) it is a rectangle with the left and right edges tilted inward. In my opinion, it looks better in the macOS version (first from left). The human eye prefers simple geometric shapes because they produce less visual noise. Also it's better for the user when clicking areas are simple shaped. In this respect, it would be worth adapting the Windows version to the macOS version. In the Windows version, the inconsistencies go a little further, as can be seen (third from left on screenshot above) when comparing the shape of the selected tab with the shape of inactive tabs in the hover state. Selected and active have tilted edges, and unselected ones on hover are straight edges rects. What's also bad is that the active/selected state and the hover state, share the same background color. These are two different states and should have slightly different colors. Someone must have slept through the UI basics lesson. I hope that there will be room for corrections in the above-mentioned issues in this beta cycle.😉

Unfortunately, nothing has changed and this functionality (split/span columns) is still not available

@Callum, can I ask you a favor? Could you please add an bug tag containing a reference number to this post. This will help us track when the issue is fixed. Thank you for logging this issue.

APub 2.4.2 Windows PRO 22H2 Something strange happens when the first page has guides from master page and you add more pages in the document Create a new document. Add guides to the Master A page. Make sure the Master A page is aplied to the first page of the document. Add more pages. The problem: After pages being added horizontal guides coming from the master are rendered on the pasteboard on the left next to the first document page, despite there is no page in this place (see attached video↓) Please fix these quirks as they degrade the user experience⚠️ APub_master_pages_guides_quirk.mp4

Ahh, you're right @MikeTo, at first glance I didn't notice that the close panel icon was on the left, so it's a macOS screenshot. However, the "Update Paragraph Style" button should still not be placed above the dropdown button, but next to it on the right😉 Placing it above, is an example how not to do the UI/UX.

First thing @MikeTO The "Paragraph Style" drop-down list, you're refering to is simply a list of options that appears when you click a button, not a combo box. You can talk about a combo box, when you're dealing with a combination of a standard list box or drop-down list and an editable text box that allows users to enter a value that is not in the list, which is not the case in the example you're refering to. Second thing: The "Update Paragraph Style" button should not be placed above the button used to reveal the drop-down list, but next to it, as in the contextual toolbar. The clickable area of a drop-down button should be protected and accessible only to that button. Otherwise, you'll run into the problems you mentioned above, such as a situation where the user accidentally updates a paragraph style even though his intention was to reveal the drop-down list, all because of a click on the right corner, what is usualy reflexively done in case of drop-down buttons. @Patrick Connor Could you please bring this issue to the attention of the person(s) responsible for the UI design? BTW, nice to see you're finally trying to improve the UI. I missed it. On the contrary, UI has a huge impact on the user experience and therefore helps companies achieve their financial goals by simply focusing on user needs. The interface should be designed with particular care, even down to the smallest details. The app should look good and be user-friendly. Without the right balance between UI and UX, you can say goodbye to potential users and wave them away as they retreat and try to find something else. Rule #1 - “Focus on the user and everything else will follow.”

Your view coincides with mine, so there are at least two of us now.😉 Whether and when this will be implemented depends on how much this feature is desired. You are the first to notice this, so answer this question yourself. Generally, regular expressions in the Find and Replace panel are an underestimated function, so it is hard to expect that improving it for tables will be a priority. I know it will be much less pleasant without the ^ token, but you can still fix those unwanted spaces, you just need to use a different strategy, e.g. you can try to target BAD|Bad| BAI| BAE preceded by \s using a pattern like [\s([A-E]{3})] with [Match case] option unchecked. Do not give up @jamakasi The time you spend on finding the right pattern will not be wasted, you will learn more about regular expressions, which will bear fruit in the future💪. Good luck dealing with those unwanted spaces in text, @jamakaschi.

Certainly, many of the issues described here are already known to management and development teams. However, testing for known issues, even obvious ones, is also important because it helps them analyze the impact of these issues on the overall customer experience. So keep testing and share your feedback, even the obvious ones. They certainly don't take them lightly😉

@stokerg For me it also doesn't refresh automatically after I drop the file. It is necessary to interact with the panel to force a refresh. I checked using PNGs and SVGs. This happens with every file. So @stokerg it's possible that this is a problem for a larger group of users, but you don't see it in the reports, because perhaps not everyone will report that it also applies to them.

I don't always agree with you, but that's probably the case. There is no reason to be disappointed. This is a bit of an exaggeration. On the contrary, the reorganization of the beta forum is a sign that a new beta version 2.5 should soon see the daylight.

@kat This is not a top menu but context toolbar for text frame. The context toolbar always updates to show the options available for the currently selected tool. This button (marked in red rect in above screenshot) is used to update paragraph style. When you make some changes (overrides) in paragraph it is used to update the paragraph style to include those changes. The mere fact that it is not dimmed, i.e. disabled, means that there are some overrides in the paragraph. Am I right @MikeTO, or maybe I mixed something up? That's right, you nailed it in the first reply post👍.

Hi @jakamaschi, welcome to the forum. Nice of you to join.🙂. Indeed, it does not work as it should and I will clarify a bit, it is caused by an incorrect decision regarding the way of comparing the content of the table (text) with the regular expression pattern, namely treating it as a whole as if we were dealing with one text frame. Hence in case of ^ token we have unexpected results and begining of text in cells is not always recognized as beginning of a line. Why does it work this way with tables? I don't know, you'd have to ask the developer(s) who implemented it. @DWright Can you ask someone who has implemented this why regular expressions are processed this way for a table? @jamakaschi The solution to the problem you briefly described would be to treat each cell separately as an independent text frame, and compare those frames text one by one against regex pattern and show the results in Find and Replace results list. Screenshot of results for [^\s([A-Z])]↓(click to enlarge)