-
Hi again! Thanks for your previous assistance. After applying your tips, I conducted some tests on the local iModel that I downloaded using the briefcase. However, I'm encountering issues with modifying properties following those changes sugested. To allow editing, I enabled isPropertyEditingEnabled to true in the viewer, which made the input box appear, but it doesn't actually modify the property when I press enter. I'm seeking guidance in this part. From what I understand, I could possibly resolve this by using an RPC interface to communicate with the app's backend, perhaps using updateElement as suggested by another maintainer. Thank you again for posting those links!. In my main project, I used RpcInterface from @itwin/core-common to create a custom interface, and I think this might be the correct approach to locally modify properties. Would this method be appropriate? or maybe its a better aproach? Additionally, I have a question regarding what exactly constitutes an "element" within this context. For my tests, I used a snapshot to access the iModel that i previously download and printed it, but I'm not seeing anything related to bis.elements or other tables that exist in the BIM file. It seems like I'm accessing iTwin information rather than the iModel specifics. Could you clarify this for me? And again thanks for your help! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The property grid component doesn't handle updates - you'll have to do that yourself. Assuming you're using the widget from
I'm sure what you expect to see there, but the |
Beta Was this translation helpful? Give feedback.
The property grid component doesn't handle updates - you'll have to do that yourself. Assuming you're using the widget from
@itwin/property-grid-react
, you can supply theonPropertyUpdated
callback to be notified about the change in the UI, where you can initiate the actual change in the iModel.