dan20047 Posted September 17 Posted September 17 I use a variation of the ssx.lsp to select objects in the drawing. In Bricscad v15 using (sssetfirst ss1 ss1) would both activate grips and activate the properties window to show info on those objects. For example select all blocks with same name, I could quickly edit the attribute value for all of them. I'm testing upgrade to v26 and the properties window no longer activates unless I manually toggle the property preview button. Is there a system variable to use the old behavior? Here is the simple code: (setq ss1 (ssget)) (sssetfirst ss1 ss1) 1 Quote
mhupp Posted September 18 Posted September 18 I usually just keep it docked on the right side and use ctrl+1 to open it if needed. any of these will open properties (command "Properties") (command "PR") (command "CH") (command "MO") 2 Quote
dan20047 Posted September 18 Author Posted September 18 I have dual monitors and properties is always open, it just isn't recognizing objects selected with sssetfirst. However you gave me the idea to toggle it off/of which does refresh it to show the selected objects. Thanks. (command "Propertiesclose" "properties") Quote
mhupp Posted September 18 Posted September 18 (edited) looked at your code closer the first argument needs to be nil in sssetfirst left over from legacy code. https://help.autodesk.com/view/OARX/2023/ENU/?guid=GUID-4076CD9D-1C66-4C73-ACC0-3A6CD0B0D2D8 '(sssetfirst gripset[pickset]) 'gripset 'AutoCAD no longer supports grips on unselected objects, so this argument is ignored. However, if gripset is nil and no pickset is specified, sssetfirst turns off the grip handles and selections it previously turned on. 'pickset 'A selection set to be selected. (setq ss1 (ssget)) (sssetfirst nil ss1) Edited September 18 by mhupp Quote
dan20047 Posted September 18 Author Posted September 18 You're right, but it doesn't change the properties window behavior. I wonder if this is a Bricscad bug related to the PropertyPreviewDelay setting. For the sssetfirst syntax, I can't be bothered to look up the correct format so I always use the variable in both locations, since the help file says the first argument is ignored. Quote
BIGAL Posted September 21 Posted September 21 I am using V25 had properties window open, ran code by @mhupp and it worked properties window displays and objects are highlited. Quote
mhupp Posted September 22 Posted September 22 (edited) A bit of googling check your version is past 26.2.07. can't check because i don't have V26 A regression in BricsCAD V26.2.5 caused the Properties window and other GUI components to stop updating during LISP execution, particularly when waiting for user input. This issue was identified as a regression and has been fixed in V26.2.07 (and subsequent builds). If you are experiencing this behavior: Update BricsCAD: Ensure you are running V26.2.07 or a newer version where the fix is included. Check System Variables: LISP scripts may inadvertently set FILEDIA or CMDDIA to zero, preventing dialog updates. Ensure your code resets these variables or uses an error handler to restore them upon cancellation. Alternative Property Access: For object properties not updating via COM, BricsCAD supports non-COM functions like (getpropertyvalue), (setpropertyvalue), (ispropertyreadonly), and (dumpallproperties) which work across Windows, Mac, and Linux. Edited September 22 by mhupp 1 Quote
dan20047 Posted September 22 Author Posted September 22 Thank you Mhupp for looking into this. I'm on v26.1.05 and planned to update before posting question to Bricscad support. I've also experiencing delays of over a second in layer properties toolbar registering layer changes by lisp command. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.