thomaso
-
Posts
11,037 -
Joined
-
Last visited
Posts posted by thomaso
-
-
1 hour ago, Old Bruce said:
Now I Don't Know its Name.
May be you use "ideas" as names, not values? I can imagine that you might get irritated if your color for instance "sky blue" or "green 4" would get a different name by the application. What I meant are names with values only, as shown in my screenshots: I changed a blue into a yellow - but the name (values) remain as blue. This might become disturbing especially if you use global colors and use to alter them. I showed it with this two very different colors to make it more obvious. In reality the color change might be more subtil and a wrong name not such obvious.
1 hour ago, Old Bruce said:I think you are just having some fun here.
No, I am wondering, why this menu does tell me. It gives the impression I have to be careful. Usually you can undo every change you do in a file – and therefore a warning would make sense only when an undo would NOT be possible.
-
In the list view of the swatches pane any new swatch gets an auto-name with its defined values.
Unfortunately these names don't auto-change when the color definition got changed by the user. This results in wrong swatch names, both for global and non-global swatches.
To avoid wrong names the user has to rename any swatch manually after changing its color. To fix the name it needs several clicks to the manual renaming option window.Suggestions:
– auto-change a swatch name when its color definition got changed
– enable renaming on double-click the swatch name
p.s.: in the actual renaming option window a hint appears: "This is not an undoable operation." – Why does it warn me that I can undo this operation?
-
38 minutes ago, stmartin said:
Also if you work with two monitors it might happen that the second screen is disconnected (e.g. from touching the cable) and all of your panels are pushed to the primary monitor. And you have to rearrange all the panels.
The possibility of saving workspaces is mandatory.
Completely agree!
Besides the missing ability to save individual option pane positions: imho the use of two monitors appears to force application crashes and makes the ability of saveable window positions more necessary. (see also window/pane positions )
-
> " ... only happens when one of the documents is offset from the main screen"
Not to me. – Might be a problem with two monitors?I just de-selected "Separated Mode" –> it arranged some but not all of the option-panes positions to a former setting + the two open doc-windows from the larger second monitor to the smaller laptop screen, behind the option pane windows. I moved them back on the larger/second monitor and selected "Separated Mode" –> that made the App crash and close.
By the way: after restart the app it was the first time (of about 15) that my individual option pane positions were not placed anywhere and somehow chaotic after the application crash.
-
A ctrl-click appears not to react mac-like & not as mentioned in the Affinity Publisher Beta Help: – For instance in the Swatches Pane:
A ctrl-click on a color swatch opens a pulldown color-pane (with noise slider instead the opacity slider in the 'original' color-pane). The same result occurs with an option-click and with a double-click (no key pressed).
Different to this behaviour the Help says:
"ctrl-click the swatch you want to remove and choose Delete Fill from the pop-up menu."In MacOS usually a ctrl-click = a right-click. This appears not to work in Publisher, different to its Help-Info.
-
In a new CMYK document a frame text appears as black by default. That's fine. Unfortunately this Black appears in the cmyk slider view of the color pane not to be = 100 K but mixed 87 C + 78 M + 65 Y + 93 K, which additionally is a rich Black with 323 % print color. This complys to the default Black definition of an RGB document.
Any chance to fix the default Black for all CMYK documents to 100 K?
-
Is it possible to save a custimized setting of window/pane positions?
It appears to happen accasionally with 2 open documents that choosing "Window" > "Merge all Windows" results in a crash and closes the Application. After reopening the app all panes are spread somehow chaotic on my two monitors and neded to get reanged.
And: how can I go back to the deafult window/pane setting? Meanwhile the tool and document and the long pane with the persona icons aren't locked anymore to the main monitors edges and partially covering the document window.
-
I'd prefer to avoide to post already existing topics. Therefore it would be very useful, to make the search option/filter "Search in This Forum" working.
At least as long the UI contains issues it would help a lot in any search for "windows" not to get results relating the Windows operating system within the Mac forum.
-
> into the “Signature” section of my profile
where is the “Signature” section in my profile?
I can't find any "signature" wording within my Affinities forums profile.
Can you deliver a screenshot of where you put it, please?
Here is mine of no "signature" section:
-
okay. "signature". now you'll guide us to "signature" - either, No, both in Affinity forums UI and in your profiles' result.
very curious now: what to get is what to see what you'll show now? :•)
-
>> Ah, where is a useful place to write system information into a forum user profile? – Is it @ "Profile Feed" / "what's on your mind?" ?
> We've not really thought about this. :(
Would you tell/show us at least where/how users feed into "What's on your mind?" will occure?
-
There is a Mac OS X feature, both system-wide and in most third-party applications, which pop-ups the file path on command-click on a documents window title . – Sounds complex but is easy to use.– Unfortunately it does not work in Affinity. ( Hm, because of its window 'tab' concept? ) – Instead in Affinity a command-click on the window title does select an object on the Affinity document page/canvas.The competitor Adobe meanwhile lost this feature in many of its programs (no, not every) – A niche/advantage for Affinity?Even more: in OS X the user may scroll through such pop-up windows content to jump to a level in finder.For instance 2 screenshots:
-
just curios: what beta was "beta 5" which I found in some posts? I really would appreciate a look-up table with dates, names, numbers, features, fixes ...
(and I wonder that you, Serif, seem not be interrested for your own use)
this is a question only, an interest. It's neither a request nor about a bug. More a suggestion than a demand.
-
I had posted questions about understanding beta, unfortunately within a different topic. So I ask here again:
> forums structure: by beta? = by date ? Shure?
The answer #3 makes me assume any post "knows" about users beta version simply by posting date. (Easy for new posts, no need to look up and type a version number)
Otherwise it might be useful to know a particular beta version to a particular posting.
Occasionally it happens that I search in the forum for tags (nice support!) and end up in reading about a "beta 5" within the search results – whereas my experienced version names sound like "1.0." and "17644", "17832", ..."18306". – Five digits versus digit "5".
So I wonder if Serif would want to add a forums level about beta info: names, dates, changes ...
Different to topic "Beta Update" it would list- or table-like 'easily' show facts, not comments. Read only.
-
> forums structure: by beta? = by date ? Shure?
Unfortunately I had added some questions about a totally different topic above. The quoted question meanwhile got sort of answered by TonyB: https://forum.affinity.serif.com/index.php?/topic/762-does-a-beta-update-overwrite-previous-beta-behavior/&p=2683
-
Okay, thank you, this infos do help.
I'll keep only the most recent app version now.
-
> if I've upset you in any way
no, you did not. Also, -_- , I feel sorry if my reaction did sound like beeing upset.
I just got confused and/but felt shure you want to be informed about any such users' insureness. This is what 'beta' is about, right?
However, just pls make shure not to 'surprise' any not [fixed] issue or wording in the a beta.
btw: I am a youngtimer in this forum: there are posts about 'beta 5'. – Long time ago? I experience beta names like "17644" or "18089".
I feel shure it would help anyone if you would use one strictly consequent naming for beta versions. And for any users posting, too, if needed. Up to you: forums structure: by beta? = by date ? Shure?
-
@matt, @andy,
your reply in https://forum.affinity.serif.com/index.php?/topic/560-selection-marqu%C3%A9-tools-constrain-aspect-ratio-and-slow-speed/&p=2336 does irritate me.
I don't see any tool called "select" besides a various marque tools in pixel mode – whereas a beta mail mentioned "Select tool ... constrain aspect ratio" and matt asked/replied "I assume" concerning my initial question.
Just in case Affinity has more than the the rich bunch of Marque Tools of pixel mode ("persona"?
you might want to consider to define/name them accordingly in the later manual & online help. (compare 2 screenshots attached: "marque", "selection")
(i'll check in next beta: marque: constrain aspect ratio – and let you know here)
-
... or is it usefull/working to have more than 1 beta installed to compare versions?
Usually I do keep the previous beta versions to be able to compare just in case. Last week it happened that a beta appears to have overwritten a feature which - as far i remember - did work well in its previous beta.
So I wonder:
Are beta versions independent to each other – or do they use some common files?
In other words: Does a former beta still work exactly like its original beta stage - or are some files in common use and features get overwritten by a beta update (pref, system, library files)?
-
@ Andy, I might misunderstand you: To me you sound to think it can't be solved or can't get any influenced by Affinity?
(Yes, nowadays: I am aware this request isn't general GUI of mac. And as if blocked-by-apple for 3rd party developers.)
Serif Affinity occurs close: All but 1 application window opens as saved, both in position & size.
Only the document window lacks in intuitive usage. – Much work?
Appearently a system main menu bar influence issue. – Indeed?
This topics desire got solved a while ago step by step: whereas InDesign CS4 still needed the user to click a script to fit a documents window according to the users monitors and application-panel setting, CS5.5 simply did remember its documents window position & size by default. Such a script for instance:
tell application "Adobe InDesign CS4"
set Disp to (do shell script "system_profiler SPDisplaysDataType | grep Resolution | awk '{print $2, $4}'")
if Disp contains "1920 1200" then -- your screen resolution
set bounds of layout window 1 to {-1200, -240, 0, 1680}
end if
end tellHm, aha, p.s.: some applications behave likewise by default. – In lack of a 'document window'? – Those do remember their windows positions & size. For instance:
• Mac OS X (Finder ... & various system tools),
• Browsers (... Firefox, Chrome, Safari),
• Cyberduck, ... • Carbon Copy Cloner, ... • DeepMeta, ...
• Garage Band ( including its document windows:-)
@ Andy, Mobile computers, occasionally docked onto additional fixed placed monitors, will happen more often. – Agree?
-
Nobody with two monitors? – I need to drag every document window from the macbooks (start-) screen to the second but larger monitor and aditionally need to drag-scale each documents window size to fit between the panels/options/panes/palettes windows. This is a behavior I haven't experienced for ages, [nowadays to me only "Photomatix" ('HDRsoft') occures this way.]
Am I doing any wrong? Am I want to much? Are two monitors more than 'normal' (=usual?) for macbook, ipad ... or nowadays hardware 4K screen resolution with multiple monitor support?
I attach screenshots of a 2-monitor-situation (15''+ 24'') – and I do trust AndyS post: https://forum.affinity.serif.com/index.php?/topic/661-option-drag-to-copyduplicate/?p=2317
-
I want humble recommend to develope Affinity strictly mac-like according GUI (shortcuts, key commands, buttons, windows, ...). It has been also consistency, consequence which made and makes mac applications so intuitive.
Less for my convenience but rather for marketing reasons. I definitly would feel sorry to see Affinities success risked or reduced by breakings with such 'rules'.quote (Matthias, #6):
> "The reason for this non-standard behavior seems to be the selection feature: Alt-dragging changes the way elements are selected."
Agree. I'd exspect the cmd-key to alter a selection instead. For instance in mac finder to add/reduce in a bunch of selected files or in InDesign or Quark to jump between object selection of (child-)layers. – So it appears Affinity should simply turn cmd to alt/option and vice versa in affected cases.
-
@ lenogre,
fyi, a duplicate function already does exist via menu 'Edit' and/or keys: 'command-J' or 'command-C'+'command-V'.
Whereas this topic requests for a duplicate function via mouse-drag + use of mac-like 'Option'-key while dragging.
@ MEB,
> There's already a shortcut to do that: cmd + drag
Aha, good to know. Any reason for 'cmd' instead mac-like 'option'-key to duplicate any object, intuitivly?
-
you might want to consider to define/name them accordingly in the later manual & online help. (compare 2 screenshots attached: "marque", "selection")
color slider & values for tints
in Feedback for Affinity Publisher V1 on Desktop
Posted
If in the color pane in tint slider view a tint color becomes added as swatch – than the sliders & values of that swatch don't show its real value but the value of the former 100% tint.
Or shorter: sliders ignore tints, the tint slider excepted. In any slider type / color system.
For instance: 50% tint of 100 C + 50 Y shows in the sliders 100 C + 50 Y, whereas its real values are 50 C + 25 Y.
That means you can't know for shure the values of a swatch which got created as tint. Neither its name nor its slider values appear as realiable.
Related issues:
• if you hit the swatch name and, in the pop-up window, hit the pipette symbol or the tiny color circle besides the sliders pulldown menu – than the color changes to the sliders values and the created tint is lost and overwritten by the 100% of the former color.
• if you define the origin color as global color the dependency gets lost as soon you create a tint: Changing the origin color does not affect its child, the tint. A tint of a color, even of a global, appears not to be related to its mother.