Closed panditthecoder closed 7 years ago
Thank you for reporting this issue.
We could confirm it and will fix it.
This should now be fixed. Renaming from object screen and browser should update in the respective other place.
works as expected. can be closed
Thank you for testing again - closing this issue now.
Another issue - usability
I clicked on the object name in the left panel (not in the browser section) and edited the name. clicked on the 'tick' mark to accept the change. the name changed in that panel but did not change in browser panel (see image)
Logged out and back in and the changes were showing correctly. (see image).
realized that i had not checked the recent tab. wet there and it was showing the correct name. however, that was because I had logged out and back in. so went back to the 'my objects' tab, clicked on the object to bring it to the left pane for editing, and changes the name again - as expected, the name change did not reflect in the 'my Objects' list but did reflect in the 'recent tab when i clicked on it. (see image)
and lastly, went back to the my Objects tab to ensure that moving between tabs did not refresh the data but it yet showed the old name (see image)
IMHO, allowing users multiple ways to achieve the same objective (in this case renaming) is a recipe for disaster unless the objects are encapsulated perfectly and changes in one object trigger all related changes. Why do you need the ability to rename the object by clicking on the name - and if it is so, why not just call the same routine (not sure if it is being done or not) for rename in the browser ?
After typing the previous sentence, just for kicks, I went to the browser section to check if the rename was working correctly. clicked on the same object and clicked the 'Rename' icon. renames the object and as expected, it changed the name of the object in the 'My Objects; list as well as in the 'edit code' window. However, when i clicked on the 'recent' tab, the old name yet showed up. (see image)
so in a nutshell.
I have not check the 'pin' functionality - suggest you check that as well while fixing it.