DarkClown

Final Version of Publisher crashing here as well ... Crash Report attached. Backtrace.zip

As already experienced in AP and AD the Publisher sometimes has a serious issue with a permanent redraw of the screen when just MOVING the mouse (not clicking anywhere). It does not appear, when the mouse is untouched. This needless flickering drives you crazy. Sometimes it is gone when you activate other applications. For example each time I activate a screen capture program to record the effect it is gone. It occurs with an ordinary mouse as well as with my wacom tablet. Cheers,. Timo

I'm using the Foxit Reader and don't see the problem as well ... So I guess it's as explained above: a display/Adobe problem ...

Add this one to it ...

Just found this - might be related to the problem:

No, it was created plain from within publisher... Only the bg pic was imported ...

Frankly it was nothing specific. Can't recall what I was doing. I do remember it's not an reproducible action. It's just like publisher suddenly stops reacting.

Just crashed again ... found something before the restart: Backtrace.zip

Among some other behaviors I don't get - this is something really annoying. I have a table with 3 columns and 2 rows (video). The second row is already larger than needed (why)?. There are no additional spaces or anything else that would add to the space below all texts in the second row. Now when I click into one text field in the second row the table already extends automatically in height. Adding just one letter of text (without a line break) and deleting it again continuously increases the hight of the table until it extend all documents. So whatever I do the length of the table is increasing (to be more precise: the height of the second row). In the second part of the video I just extend table height by simply clicking into the text and pressing the "Del" key. In the video I disabled some less important layers to make it easier to see ... Any ideas? Or is it by default and I don't get the concept? Cheers, Timo See the video here: table.avi

The reports folder is empty (even though the program crashed many times). But it simply stops working. I can't event get the focus on the app again. I do get offered a recovery file on restart though.

It's a bit scary that you plan to release .399 as final. Even with very simple 1 page documents including 1 table, 3 textboxes and a graphic I get constant crashes of the program. Happens under various circumstances. Copy from publisher and pasting things in again, coming back from another application. The program just stops and isn't responding any more. I can only kill it through the task manager. No error message and no reaction any more. Frankly spoken this is far away from being a release candidate (and I bought it already) Cheers, Timo

There still seems to be a problem with the Wacom Tablet (using Intuos 5). Right mousebutton hardly ever works. But also left button refuses to work on some fields. When you try to increase or decrease the number of rows in a table it is impossible to change the number of rows by left-clicking on the little arrows. You can't even give the focus to the edit field with the number of rows. It works perfect with the mouse. (Using latest Beta .399) Cheers, Timo PS: this problem is not always reproducable

Just a question for my information that is not based on a special product but more on the used algorithms: When you have a gradient with a mid point how did you implement the situation when you completely shift the midpoint to one extreme (0% or 100%). Do you say mid point is always the 50% (color/opacity) of the two side values? And what does happen, when this mid point (assumed it's a 50% point) is the same as the 100% point? Since mathematical-wise this would be an undefined situation it's up to your interpretation. Example: You have a gradient from 100% White to 100% Blue. A linear midpoint will be in the middle between those values giving you a 50% Blue. Shifting the 50% Blue midpoint now to the very end of 100% what will the gradient be like? Linear between White and 50% Blue (What I would have guessed but it seems to be implemented differently) or still some kind of curve still reaching 100% at the end (what logicalwise would be incorrect but a lot closer to your implementation). Just curious .... because it didn't work the way I expected it ...

I watched the explanation of Sean ... but this seems somewhere between just mind boggling and ridiculous ... It would just need two different cases to differentiate gradients with a center and with a start and beginning and apply them accordingly. And maybe make it obvious which is applied where. When the user applies a gradient (what is by default a LINEAR gradient) he would expect it to be valid for the whole path - not only 50% of it. Maybe it would be helpful if the gradient availability (valid area, start & endpoint) is shown within the object. The way it is implemented right now hardly anyone will understand what's going on. So even if we take this crazy approach as "intended by default" (LOL) it still is a fact that the linear gradient is only applied to HALF of the path and not the whole path as common sense would assume. And of course I ask myself, why is it implemented differently in AP and AD?

There seems to be a bug (not only, but more severe) in Publisher whe you try to apply a gradient to a path. 1) When you draw a path, select it, click on "Stroke" (the path is still uni-color) click on "gradient" - a nice gradient is show but not reflected on the selected path (this is inconsistent). From my understandig the path instantly should reflect what the dialog shows. (would call that a workflow hick-up not a bug) 2) If you now move the midpoint from 0% to 100% the result only affects a part of the path (this is a bug) - See attached file. 3) A major problem I see in the way the gradient is implemented for a path is that it's just an "overlay" from a left side to right side gradien - and not a gradient along the path ... this leads to ridiculous ways the gradient/path looks like (seems to affect al Affinity programs - see second screenshot from AP with just 1 path and a gradient - don't even know why the path partially is cut of on the left) - and you can't even define the angle of the overlaying gradient so it's completely static. I guess this needs a serious rework.. Cheers, Timo