V4 beta Sep-10-2020 available now
 1-20  21-40  41-60  …  101-118

Next
 From:  Michael Gibson
9942.1 
New Sep-10-2020 v4 beta now available at http://moi3d.com/beta.htm .

Still not quite finished but really close! Exporting dimensions to PDF/AI formats is still in progress and almost there but I needed to release this new beta now because the current beta expires tomorrow. It has been quite a while since the last beta, please let me know if you see any new bugs surface in this release. It won't be much longer before v4 will be wrapped up.

New stuff:

Updated DXF - support import/export of dimension entities.
    Import of TEXT, MTEXT, LEADER, and DIMENSION (linear, angular, radius/diameter sub types) is now supported. MoI will export dimensions to MTEXT, LEADER, and DIMENSION enties.

Update annotations, add model units scaling behavior.
    There is a new option for annotation behavior under Details > Annotation properties > "Scaling:" which has options for "Scaling: By screen size" or "Scaling: By model units".

    Scaling: "By screen size" works the same as the earlier v4 betas where text and arrowheads stay the same size on screen independent from the current zoom level.

    Scaling: "By model units" is a new option that makes the text and arrowheads to behave the same as geometry, where it is fixed at a certain unit size (given by the Height: field just after it) and will display larger or smaller when you zoom in and out. This option gives better compatibility with other CAD programs since almost all other programs work this way. When you import dimensions from DXF or from a 3DM file created in Rhino they will default to using this method so that things like title blocks where there are lines or other geometry making a table with text inside it will work as expected.

Finished the AnnotationText and Leader command dialogs.

Updated show points for dimension leader. Allow delete of selected edit points for leader objects.

Handle file write errors - an error dialog will show now on file write failures like if the system ran out of disk space or permission denied.

3DConnexion updates:
    - Updated 3dx default speed on Windows. On Windows 3dx translation and rotation speed was too fast, implement same default speed as Mac.
     - Add "Reverse roll" setting in Options dialog under Options > View > Rotate/Pan/Zoom options > 3DConnexion options. Requested by Fred in the forum here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.30
    - Also added individual settings for reversing twist or tilt in moi.ini, under:
    [3Dconnexion]
    <...>
    ReverseTwist=y
    ReverseTilt=y

Update SaveAs to STEP/IGES/SAT formats for hidden objects.
    By default don't write hidden objects to STEP/IGES/SAT formats when doing a SaveAs, unless turned on in moi.ini under:
    [NURBS Export]
    WriteBlankedObjects=y

    Also fixed regression in v4 where the blanked flag for hidden objects was not being set on IGES and SAT export.

Update History
    Enable face extrudes and the Rebuild command to trigger history updates.

Curve offset overhaul - Improve curve offset robustness:
    1 - when extending a line make a new analytic line as the result and use an analytic line/line intersection when possible for more accuracy.

    2 - Update how convex corner processing is done to avoid getting little loops which could confuse trim classification and were not getting trimmed out with shallow angle polylines as reported on the forum by Yanik here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.47

    3 - Do a better job of selecting intersections and screening out wild results from G2 reflection type extension. Should eliminate crazy looping extensions.

Update grid axis display colors
    Add in Z axis color option under Options > Grid. Grid axis lines are now colored according to their 3D orientation, so for example if you set the Z axis color to blue, then the vertical axis line in the front view will be colored blue. Previously the grid axis lines were colored the same in all viewports. You can re-enable that previous way by a setting in moi.ini :
    [Grid]
    <...>
    UseOldStyleGridAxisColors=y

    Also added in an option for displaying the z axis grid line in the 3D view, under Options > Grid > "Show grid z axis in 3D view" checkbox.

Update IGES export
    Add an option under Options > Import/Export > IGES options > "Write solids as" for writing out solids as either an IGES type 186 "Manifold Solid B-Rep" entity or whether to write them as individual separate surfaces as MoI v3 and earlier always did.

Update Draw solid > Text command - font styles
    Add a Style: option to the Draw solid > Text command to make it possible to access styles of the font other than bold/italic. Requested on the forum by Javier here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=8766.1

Update error message when command not found.
    Pop up a "command not found" dialog instead of a script exception dialog if trying to exec a command that was not found in any command folder.

Update Help > About dialog
    Add links for showing license keys and EULA from Help > About dialog. The license key dialog also has an option to clear out license keys.

Detailed object properties dialog
    Implement undo for annotation property changes in detailed object properties dialog.

Update detailed properties panel types report
    Add reports for all curves, all edges, and all brep edges if there is a mix of different types so there is one label that can be targeted for grabbing all edges or all curves instead of needing to shift+click on both "Open curves" and "Closed curves" for example.

Add scale factor option for SubD import, in moi.ini
    [SubD Import]
    ScaleFactor=1.0
    requested by Tudor in the forum here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=8665.109

Update annotations bounding size
    Don't include annotations in the bounding size for the edit frame or the properties panel, unless only annotations are selected.

    There is a moi.ini option to include annotations always in these sizes:
    [Annotations] IncludeAnnotationsInBoundingBox=y

    Discussed in the forum here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=9526.30

Update persistence of "Mesh angle" option.
    On startup, clamp the value for Options > View > Meshing parameters > Mesh angle to be between 10 and 45 degrees. It can be set lower by a startup script.

Update annotation text display - substitution fonts
    Enable use of substitution fonts in annotation text rendering. This will automatically switch to a fallback font if the current font does not have glyphs for unicode text characters being displayed.

Update sub-d import
    Use mesh object name in sub-d obj file conversion, and merge styles with the same names and colors. Requested in the forum by pafurijaz here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.142

Update edit styles dialog.
    Show gray text on styles with nothing assigned to them same as the scene browser. Requested by pafurijaz in the forum here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.148

Update object dragging
    Option for disabling object dragging so clicking on objects will only do selections and not any drags.Set under moi.ini under:
    [Selection]
    <...>'
    DisableObjectDrag=y



Bug fixes:

Fix window un-maximize bug on Windows - Fixed bug where the restored window position used for un-maximizing a window would keep growing larger on every run.

Updated selection with filters on - if a selection filter is active, when clicking on an edge or face object to select it do the selection update immediately on the mouse press instead of mouse release. Fixes a bug reported by pior in the forum here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.24

Updated hit testing. Fixed bug where edge boost for selected breps was happening even for objects with selection lock on them. So in the case of boolean difference, the base object was having its edges boosted over top of any standalone curves in the same spot, preventing them from being selected. Fixes a bug reported through e-mail by Vladimir.

Fixed annotation text bugs with text anchor property. The text anchor property was not persisting properly for all values.

Fixed a bug with importing a DEGENERATE_TOROIDAL_SURFACE surface type through STEP format.

Fixed a chamfe/fillet bug with skinny surfaces. If a chamfer surface was skinny (less than 10*tolerance across) it was possible for the chamfer surfaces to get connected improperly since it took just the first one within tolerance instead of the closest one.

Fixed a bug with keyboard shortcut handling on Mac with a Japanese keyboard. Reported on the forum by nemuneko here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.39

Fixed shortcut key bug where cpaslock key was being interpreted as the letter "A" key.
Reported on the forum by nemuneko here: http://moi3d.com/forum/index.php?webtag=MOI&msg=9660.39

Fixed bugs with dialog size and positioning.
Previously when showing a resizable dialog, if there was a saved size from a previous use it would restore that same size. The bug from that was if the dialog size was done on a high resolution monitor and now the use has switched to a different screen the saved dialog size could exceed the current screen resolution. Fixed by limiting saved dialog width and height by current screen size. Also if a saved position for a dialog will be used, check if it is visible on screen before using it. Additionally, don't allow resizable dialogs to shrink to down 0 width or height. Fixes bugs reported through e-mail by James.

Fixed sweep bug - Freeform sweep framing had a bug when rail segments were anti-tangent. Fixes a bug reported through e-mail by Pilou.

Updated dimension text rendering - Y positioning for glyphs used incorrect rouning. Was causing noticeable mis-positioned glyphs when using Gill Sans 18 pt font on Mac. Fixes a text display bug reported through e-mail by James.

Variable radius filleting - linear blend fix. Fixed a bug in variable radius filleting with "linear blend" option where fillet surfaces were not being extended properly. Fixes a bug reported on the forum by Dan R here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9753.1

Fixed arrowhead bug - outside dimension arrowhead lines not placed correctly on larger scaled objects. Fixes a bug reported through e-mail by James.

Fixed dimension feet & inches display - for feet&inches, check if the font does not support any Unicode fraction characters being used and if not replace with long form text like 1/2.

Fixed STEP/IGES import of composite curve entities with G0 discontinuities. Look for G0 discontinuities in imported curves and break those out to separate curves.

Fix file dialog bug - Fix bug where file open dialog called by script was not returning empty string when canceled. Fixes node editor bug reported in the forum by Wayne here:
http://moi3d.com/forum/messages.php?webtag=MOI&msg=7713.880

Fix Extrude bug with end caps disabled - When making a curve extrude with end caps disabled, a brep with disjoint shells would be created if there were any interior holes in the extrusion.

Update sweep - true up rail segment ends. If segment end tangents are within 2 degrees of tangent, true them up to be exactly tangent if possible. This can improve corner mitering fails with segments that are nearly G1 but not quite. Fixes bug reported through e-mail by Salvatore.

Fix curve fillet bugs -
    Fix curve filleting bug reported by Cemortan_Tudor in the forum here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=8665.97
    and also another curve filleting bug reported a long time ago in the forum by macray here:
    http://moi3d.com/forum/index.php?webtag=MOI&msg=4958.1

Fix select last created not working with drag/copy. Reported by Tudor in the forum here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=8665.115

Fix bug in orient line / line
Fix bug when line directions pointing opposite each other. Fixes a bug reported in the forum by Karsten here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=9476.422

Fix file dialog crash on Mac Catalina OS
Implement fix for QTBUG-83342 for an OS bug that could cause the file dialog to crash on Mac Catalina OS.



Scripting updates:

Added Curve.getIsTangentEdge( AngleToleranceDegrees /* optional, default = 2 degrees */ );
    - returns true if the 2 surfaces on either side of the edge are tangent to each other.

Added CurveSegment.getIsG1ToAdjacentSegment( 0 /* 0 for start, 1 for end */ );
     - returns true if the next segment at the start or end is smooth to the current curve segment.

moi.filesystem.shellExecute(), added wait for finished parameter.
    moi.filesystem.shellExecute( path, params, wait ) now takes an optional 3rd boolean parameter for whether to wait until the called process has exited before returning. When used, the return value from shellExecute() is an object containing an .exitCode property for the integer exit code of the called process and an .output string parameter for
…[Message Truncated]

View full message.

EDITED: 27 Oct 2020 by MICHAEL GIBSON

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Frenchy Pilou (PILOU)
9942.2 In reply to 9942.1 
A small start for French translation before the second wave!
https://moiscript.weebly.com/v4-quoi-de-neuf.html

else here the French Version of the UI! :)
https://moiscript.weebly.com/uploads/3/9/3/8/3938813/frenchstrings.txt

EDITED: 11 Sep 2020 by PILOU

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.3 
V4 beta Sep-10-2020 release notes added above.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  stefano (LIGHTWAVE)
9942.4 In reply to 9942.3 
Like the dimension tools...especially that they are separated in 'objects' view

@Michael & others, please can you see if this 'unlikely' bug is happening.

Draw any object, make sure it is selected.
Press tab
click the coordinates field
numeric entry box appears.
Don't use the keypad.
type something random into the command/coordinates box
I initially accidentally used "bb", you should see programme crashes.
I can repeat this with any text "abc" and it will crash everytime.

EDITED: 12 Sep 2020 by LIGHTWAVE

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Frenchy Pilou (PILOU)
9942.5 
Complete list of news in French done :)
https://moiscript.weebly.com/v4-quoi-de-neuf.html
---
Pilou
Is beautiful that please without concept!
My Moi French Site My Gallery My MagicaVoxel Gallery
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.6 In reply to 9942.3 
Hi Michael,
Regarding the ini file, i keep mine in the root install.

MoI Rewriting my mesh angle parameter. I keep mine set at 4.0

It keeps resetting it to 10...

It now wants to find it in the app data directory i store in my root install also....

Any help? Is the somewhere else to eliminate it for the root ini to default or be read?
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.7 In reply to 9942.6 
So if I run MoI as admin, it will look in my root install, but still wont write the mesh angle value.

If I run it normally, it needs to find it in the appdata folder, (stored in my root install) or it defaults to an unknown ini and location.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.8 In reply to 9942.7 
I just tested with the January beta, which still works today, and it works as expected, reading the mesh angle and allowing it to be set.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.9 In reply to 9942.4 
Hi Stefano,

re:
> @Michael & others, please can you see if this 'unlikely' bug is happening.

Yup, I can repeat that. Seems to be stuck in some sort of infinite loop. I'll investigate it for fixing, thanks for reporting it!

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.10 In reply to 9942.6 
Hi Burr,

> Regarding the ini file, i keep mine in the root install.

Check out the shortcut key you were using to launch the previous MoI beta, is it set up to pass in a command-line parameter to moi.exe to give it the location of the moi.ini file? If so then you'll need to set the same thing on the new shortcut too.


> MoI Rewriting my mesh angle parameter. I keep mine set at 4.0
>
> It keeps resetting it to 10...

Yes, it's a kind of "guard rails" function, I keep getting problem reports from people who have set it low without really being aware of it and then later on when they open a large file it consumes much more memory than they were expecting.

I'll set up a flag in moi.ini so you can tell it "no guard rails".

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.11 In reply to 9942.6 
@Burr, also for mesh angle one thing you can do now before the "no guard rails" flag is set up is to make a text file like SetMeshAngle.js inside the appdata startup folder, and put in this: moi.view.meshAngle = 4.0;

That script will then run at startup and should set the mesh angle for you.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.12 In reply to 9942.11 
Hi Michael,
Setting the mesh angle with a script in the startup folder works great.. Thanks.

Just so I am clear, this "Gaurd Rail" function is "NEW", Correct?

It didn't do this previously.

So, the mesh angle ini setting is obsolete if you can only set it for a current session within the UI. But the new flag you mention could make it relevant again?

(As a side note, I understand the explanation of "Low mesh angle being persistent can cause issues". I just want to understand the best way to move forward)

Thanks again for all the hard work.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.13 In reply to 9942.12 
Hi Burr,

re:
> Just so I am clear, this "Gaurd Rail" function is "NEW", Correct?

Correct.


> So, the mesh angle ini setting is obsolete if you can only set it for a current session
> within the UI.

It still works as before for values between 10 to 45 degrees.


> But the new flag you mention could make it relevant again?

Yes, the new flag that I'll add will make things behave same as before.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.14 In reply to 9942.12 
Regarding the ini location. If I start MoI from the install location (Program files) Clicking "Edit Ini" from the options dialogue shows a location of "appdata" folder located in the root folder.

If I run MoI from a copied backup location, or my USB install. then the edit ini location shows as the root.

So basically, I have 2 ini locations to keep.

It "Should" just read the root one and be done, yes?
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.15 In reply to 9942.13 
Thanks, clear now on the new gaurd rail. Will look for the new flag also in a future release.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.16 In reply to 9942.14 
Hi Burr,

re:
> Regarding the ini location. If I start MoI from the install location (Program files) Clicking "Edit Ini" from
> the options dialogue shows a location of "appdata" folder located in the root folder.

Yes, that's the default behavior.


> If I run MoI from a copied backup location, or my USB install. then the edit ini location shows as the root.

If you have copied the moi.ini file into the same location as moi.exe and it has write access to the file then it will use the one that is in the same folder as moi.exe .

When MoI starts up, it first checks if there was a moi.ini file passed in as a command line parameter to MoI.exe, if there was then that's what it will use.

If there was no command-line parameter for the .ini file then it next checks if there is a moi.ini file in the same folder as moi.exe and if it has write access to that file it will use that one.

If neither of those cases are set up then it will use appdata.

Some things to check if you're seeing different behavior in this beta:

- in the previous beta did you pass in a moi.ini filename as a command-line parameter to moi.exe and this isn't set up for the new beta?

- did you copy a moi.ini file into the same folder as moi.exe for the new beta but not done the same for the new beta?

- did you set the previous beta to run with elevated admin privileges (to have write access to the Program Files folder which is denied by default) but haven't got the same set on the new beta?

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  BurrMan
9942.17 In reply to 9942.16 
""""""""""""- in the previous beta did you pass in a moi.ini filename as a command-line parameter to moi.exe and this isn't set up for the new beta?

- did you copy a moi.ini file into the same folder as moi.exe for the new beta but not done the same for the new beta?

- did you set the previous beta to run with elevated admin privileges (to have write access to the Program Files folder which is denied by default) but haven't got the same set on the new beta?""""""""



No to all of those, but I have looked at previous backups of previous betas, and they have the 2 ini files. Which means my installs have been using the appdata folder located under my installation location...

This would just be an error on my part and a misunderstanding.

I'll just move my ini location from the root, next to the MoI.exe into the appdata folder located at C:\Program Files\MoI 4.0 beta Sep-10-2020\AppData...

That should straighten me out.

EDITED: 12 Sep 2020 by BURRMAN

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  pior (PIOR_O)
9942.18 In reply to 9942.16 
Congratulations on the release and bug fixes !

One remark about the beta period : it would be great to have an elegant way to warn the user about a beta period being just about to end. Of course I understand that in theory one shouldn't do serious work with a beta, but in practice it obviously happens ; and it can be frustrating to be forced to update a piece of software just to keep working on an ongoing piece (as this just happened to me at this very minute :D). Most of the time it is 100% fine, but it can get troublesome when working towards an upcoming deadline, or when cut off from the internet (not sure if the current system accounts for that). I think it would be fair to expect beta periods to at the very least have some overlap of a few days to a few weeks, while giving the user some warnings about the requirement to update soon.

There's no perfect solution to that issue of course, but I feel like it could be handled better than the way it is done at this time, which essentially prevents the user from working for a while. I hope this make sense !

That said, maybe that's just a coincidence on my end ? Not sure if the validity of the beta period is per user, or tied to the releases/established calendar dates.
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  Michael Gibson
9942.19 In reply to 9942.18 
Hi pior, yes usually the way to help out with that is to have a fairly long overlap period of several months between when a new beta is released and when the previous one expires. Usually that's what I try to do, but that didn't happen with this release, sorry about that.

I had been hoping for a while to have this be the last beta and trying to wait to release it until everything was all finished.

- Michael
  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged

Previous
Next
 From:  pior (PIOR_O)
9942.20 In reply to 9942.19 
Ha, understood - indeed I don't remember it happening during earlier beta periods, true.

- - - - -

Back to comments !

I find myself using the Image feature a lot as I mostly use Moi for 2D drafting these days. It works great overall but there are a number of little details about it that could be smoother.

- I think it would be great to be able to interact with images present in the scene without having to go back to the Image tool manually. Maybe some key combo allowing to select the image planes just like regular objects (key+click), or some clever mouse input (triple or quadruple click), or some UI widget which would enter Image mode from there.

- Once in the Image tool there should be a way to duplicate a current image. And even better, doing so in the scene state it is currently in. Either by somehow interacting with the image object itself by copy/paste, or through a duplicate button. Without that, making a duplicate of a current image involves importing it again and placing it in the viewport again, which is annoying and breaks the flow of work. At the moment if I need to have, say, 5 duplicates of a rough draft to make 5 clean variants from (which, as you might guess, is precisely what I need to do for some design work at the moment :D), I need to import and place the rough 5 times. I should really only have to import once and then duplicate from there. It seems minor but in practice it is quite a blocker, especially since each time the image needs to be "drawn in" from corner to corner meaning that for a perfect duplicate the user needs to remember to enable object snap too. It really does pile up :)

- The "Transparency" value (with 90 being very transparent and 10 being near opaque) is counter-intuitive. It should be labelled Opacity, with 10 being very transparent and 90 being near opaque.

- The numerical input field is error-prone, especially for fast users used to keyboard input. I understand that it is the same as everywhere else in the program and that many users are probably used to it, but imho it could behave much better (of course I don't know which part is tech limitation from the UI API and which part is intentional behavior here.)

First of all, there is really no need for the big keypad to show up for anyone using a keyboard (which I assume is 99% of the user base). It seems good in theory but in practice it is laggy (shows up a few milliseconds late) and visually distracting ; and any power user will just type with the physical keys of their keyboard anyways (either top row or keypad). I believe the visual keypad should be an option, probably best turned off by default. It is also stealing the cursor (making the caret disappear) which breaks the visual confirmation that the field is ready for keyboard entry so that's another way it goes against the habits of power users used to the subtle but universal visual clues of any OS.

Also, the visual keypad shows up when a field is highlighted and disappears when it isn't. It "makes sense", but it is strange for such a big UI element to be turned on by a positive input that is usually not a toggle (click), but *also* turned off by the same input (another click, removing the field highlighting). It gives the impression of a UI element that is always "just about to break" so to speak, which is problematic UX-wise.

An alternative (on top of the option to have it show up by itself or not) would simply to have a button that opens it up (see mockup). This would have the advantage of being more practical for tablet users, since hitting big buttons on screen is easier than hitting text entry fields.



Lastly in the case of the Image tool in particular, the entry field sometimes fails at displaying the current Transparency value of the currently selected image in the list.

I hope this helps !

EDITED: 12 Sep 2020 by PIOR_O

Attachments:

  Reply Reply More Options
Post Options
Reply as PM Reply as PM
Print Print
Mark as unread Mark as unread
Relationship Relationship
IP Logged
 

Reply to All Reply to All

 

 
Show messages:  1-20  21-40  41-60  61-80  …  101-118