• Content count

  • Joined

  • Last visited

About Polygonius

  • Rank
    Advanced Member

Profile Information

  • Gender
  1. Yeah, this 4 difference-pixel-"border" is what i want by doing export via export-persona. But it also transform the "content" (the real pixel) as you can see. I except that the export-persona just at this 4 pixel "border" but keep the rest it is!
  2. Please look at the picture below: 2 times the exactly same (frame) text-layer in exactly same settings (png, bikubisch). Rightside export via menu, leftside via export-persona: There is a big different in quality of rasterize. If you take a deeper magnify look, you will see that the "brothers" also not have the same size. Its extrem gentle, but it is. And maybe thats the reason, but i need the export via persona, cause it allows to export exact the high-size i need (in this case 120pix). But it seems to "transform" not just add the needed extra-space. The file-export does not export the size of the frame, just the "netto-pixel" and a 117,3 pix or so result i can not use in the target-app. In the zip there are the 2 png-exports. Archive.zip
  3. Good to know. Thanks.
  4. Thank you, but i found another way: It depends WHEN you select the color for paining. If you select before record the macro it will not taken as part of the macro, but if you choose it, during recordin g the macro it will later give you the choosen color by reply this macro later in any new document, it will overwrite the current color setting. Select a color is not listed as step of the macro, but it seems it is still existing, but hidden inside this. And there is another trap: Do not write the macro with the "back(stroke)color" as active - if you want working that color under all circumstances you must set the same back/for color, or take later part that the right one of both is in active state. Try it: Take this macro look inside and look at your for/back color. Are there more hidden recordings? It would useful to know that. Colorchanger.afmacro
  5. Hi callum, that is SOMETIMES true. In the zip are 2 macros booth painted with 255/0/0. The first one takes "its" color, the second one takes the current doc color. The second one has a step more, before painting, the color for painting was choosen after this step, so it should never influence the result, but it does. Archive.zip
  6. Right, but i´m afraid a normal user does not know how to find /"print" this. So this "implementation" is just a ask to the OS: please create a text file with sys-report. Not more!
  7. Is there any possibility to combine some "strokes" per painting as just one step? I do not want to set the color for each "stroke" separately, i want the first color is valid for all sub-strokes! Any trick for doing that? EDIT: If i set the color before the macro-painting all strokes get that color, but if i apply this macro to a new doc, the macro-paint is using the current color, but with a recolor its comfortably editable, except the current color is complete black/white or no-color. Any idea how to skip this possible trap?
  8. Yeah, i believe that too. Maybe its a special entry in system-prefrences, maybe for mouse-behavior???? For me: Some standard-Serif - behavior does not work, cause i have special mouse and help-settings... from booth: OSX preferences and BTT. They are very special and Serif could not reproduce a misbehavior without this infos. Serif would save time, if they implement a simple "create system-report" button (like after a crash) whenever you need, which listed all relavant settings and tweaks by the owner.
  9. Yeah, thats a high frequented beginner-mistake. And even i stumble from time to time about this (after mix of placing and regular open...and long names which hides the lcategory in the brackets...). There should be an option "always place jpg, png... as raster". For me its what i want in approximately 90% of cases.
  10. Not here: I tried with different angles and different speeds, all fine. Things like that are not seldom limited to an OS or other special configuration: I use AP 167, OSX10.11.6, Better touch tool 2.405
  11. Thanks for interesting. Nope, CONTAINER has not much common with macros. They can look similar, but under the hood thats two different things. Container are an concept which has improve the workflow in audio-apps (DAWs) since decades. A container is just a combo of different FX (Grafik-apps call it filter and adjustment-layer) but they are FX (except Highpass or select just green or borders… The rest of „filters/adjustments“ are FX). A container can hold as many FX you want / as your maschine can handle. And you can define ONE interactive Tweak-Box, for all parameters you want to see! For example: You put a level-adjust and HSL and a white-balance into one „container“. After some tweaking all „FX“ you will get a LUT-like result for toning/contrast. If you happy you can save this CONTAINER for later use. Later you can open this container to a picture (part of it) whre you think, it will fit. But thats the fisrt step. A container is not static (like a LUT or Macro…) You open this container and the whole FX will open as a compact group, with all FX inside, but as closed group and exactly as you „preset“ it (levels are there, HSL is there and white balance so….) But there is also an interactive panel, including all sliders on the last saved point which you can now tweak. This is quiet similar to use a macro with some FX inside BEFORE press apply! You can tweak a GUI with just the sliders/boxes you want in one compact overview. In this case maybe just the blackpoint, the red-saturation-shift of the HSL and the „tone“ of the white-balance and maybe the blend-mode/opacity for the HSL… (What sliders you see and which „default“ they have, is completly by you, by making a container-preset) You could tweak as much you want non-destructive, leave the container and come back and re-tweak what you want… in the same compact-container-overview… This is a very simple example what a container can be. A container could also be a blurr, a highpass a level a waves deformer, a recolor, a B/W and a selective color… or combine filigran expoxuer with smooth vibrande and maybe a subtil curve... or do wild stunts with maps, blurs, noise and crazy curves... its all possible and its all "saveable" and defining just the parameter you want for later use.... If you mean, you this combination often, so save it and it will appear next time in exact this group with exact this sliders you defined for fast tweak in esact this values you have stored it…. But mostly we just want dozens of special un-sharp/level/hsl or hsl/BW/treshold/blur or (my favorites) blur/noise/blend… However, most guys will usecontainert as „LUT“ or Tone-map or special-FX...… and thats nice, you can create yout own library with dozens of sub-categories and all of them keeps dynamically. But also: You can tweak containers to any point you want in a compact OVERVIEW! Containers are „liquide“ Luts or liquied SFX, or liquied Fonts, shapes....… depending of the creativity that container-maker...
  12. Ups - what a killer feature i will switch to PS. Bye, bye! Serious: Nice feature, AP does it a little bit with alt-click in canvas,... But with dozens of dozens overlapping layers on this "area" its neraly impoosible to hit what you want. Well, this feature should implement. But by implementing this, please, please overwork also this (sometimes) nasty behavior of !auto-selec a layer" by clicking anywhere in the canvas: I do not know if anyone can understand, but if you have a big BG, a fill-layer, some other "big" layers, some shapes in groups, etc -even here its hard to hit the layer you want /even with alt). But if you also have small text, or other really small, "borderd" layers it become a really puzzle. Even with alt!!!! And than this permanent blue selection-frame... how will decide if a change is good or not if this frame is bigger than the selected item in 1:1 view (big BG, smal text-item, or something similar= Yea, i can hit space to hide this frame, but by hitting space i cannot do some other advanced stunts to this item... And evry time i click (in canvas) a little bit outside, the "clicked" layer will selected. Sometimes i want just to work on this layer - it does not matter whre i randomly click in the canvas. In this case i want a "KEEP selected layer by layer panel!." Meaning: This layer is as long in focus until i "deselect" in the layer-panel... every click in the canvas does not influence the choice of active layer. If i want go back to normal behavior i just hit a special symbol in the layer-panel! State of the art its an imposition to edit SELECTIVE very small items with groups or backgrounds behind... )maybe thats more for AD relevant, but also in AP we want edit small texts on big BG... or reposition small shapes in 1:1 view... and this blue frame and this auto-selecet is the opposite help in the case... BTW: If you handle with "some" grafic-text-layer... please implementt this fast feature: Vleartext as rename the layer will also re-text the associated text in the canvas by a special key. Maybe for AP for Photography not so relevant (for me it is) but I guess at least with publisher this kind of better hitting /keeping small-layers-request will become legion!
  13. Yeah, and as i said i see this also MOSTLY more as a feature than a misbehavior, but only for this 3-slider"dialog/tool-boxes" BUT NOT for this ones, which are more remember to a text-app, like equations.... Its difficult to find here a GENERAL consens. Enter can be a speed up, instead mouseclick to "apply" and its in similar context often used for. (in my case - i´m a right-hand-man, i do not often use it much when working primary with sliders, cause "ENTER" is on my mousehand-way, so moving mouse is often faster than let the mouse and switch to keyboard "as shortcut" - Except in text-apps: here my right hand is MOSTLY on the keybord and my little finger very fast on "return"). I have set "esc" (my left hand) to things like "cancel, deselect, do not apply..." and thats really a shortcut FOR ME. But for a left-hand-man it maybe doesnt really speed up. So thats what i say: It does not matter is that common - for some people just the opposite is more useful. It does not matter WHY a coustomizer wish this, do not ask, give him this option! Thats another reason why "options" are so important for "power-users". If i had 2 apps, mostly doing the same - i would take this one, which i can more "customize". ### Excurs Apple/OSX is the opposite of custumization (but i love my 5k imac and the lack of driver-struggles each os-update and stuff like this) and Apple-Logic (its a DAW, taken from Emagic, and inherit its "complex-customization) - is an example of well customization. I prefer (for other reasons) another DAW, but Logic is a very good example how deep "customizable" can go. At least the search-field which prompts "orders" - Serif should overtake. But for version 1.x i am really happy with Serifs possibility of costumization - most apps goes never so deep: Pages & co are laugh-numbers. The holy Steve Jobs himself has decided nobody needs a right-mouse-button, so its LAW! What kind of arrogance for more than 2 decades... Apple needs very very long to confess: This was a mistake! And i´m afraid they did not learn and will need another periodes to confess: The concept of some other are better than our! What are Clowns! Well, customization is a weak reason to buy an app, but a good reason to keep old customers to us! As more i "invest" in an app, as more loyal i will be. And as more as small updates (= we see this as gifts) come, as more my loyalty will grow. The era of ONE standard-app (living in an exclusive aura of mystery / giving no details out...because we do not need, we are #1...) are completly gone! Today a developer must be also an entertainer: Custoumer want to know, what can we happen next months? End of excurse#### @MEB: Good news. But please read my semron again. Concistency is maybe not the best choice for all detail-ask. The goal is to implement a "general consistency" WITH the option to customize this, if i (for what reason ever) do not want this "taste"! A good test for implement an option or not, is maybe: if just 2 developer have a different suggestion how a thing has to come implement, than also 1000 people will have a different viwe = option need! If all dev have more/less the same opinion, so no option is need. Thats as fist-rule.
  14. Right, i mean this filter. But i guess Serif sees this "apply by enter/return" as a feature, not bug. And in most cases it is a feauture (i have no reason to hit enter/return in other filter/selection... except for doing apply. But for equations its really nasty, this reflex to hit enter/return after a line is so deep, i cannot give up). And on windows enter is not associated to apply for any filter or just equations?????
  15. Do you mean by "select" the content of the layer, not the itself with you "select" via normal mouse? You can click the thumbnail of any layer and CMD (or pendant in windows) and the "content" gets this ant-line.