-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Description
Page URL
https://docs.flutter.dev/learn/pathway/tutorial/devtools
Page source
https://github.com/flutter/website/blob/main/src/content/learn/pathway/tutorial/devtools.md
Describe the problem
The tutorial page claims:
If you select a Tile widget in the widget inspector, the property editor would show you its width (60), height (60), and the decoration property. You could then expand the BoxDecoration to see the border and color properties.
For many properties, you can even modify their values directly within the property editor. For example, to quickly test how a different width or height would look for your Container in the Tile widget, change the numerical value in the property editor. Then instantly see the update on your running app without needing to recompile or even hot reload. This allows for rapid iteration on UI design.
If you select a Tile widget in the widget inspector, the property editor would show you its width (60), height (60), and the decoration property. You could then expand the BoxDecoration to see the border and color properties.For many properties, you can even modify their values directly within the property editor. For example, to quickly test how a different width or height would look for your Container in the Tile widget, change the numerical value in the property editor. Then instantly see the update on your running app without needing to recompile or even hot reload. This allows for rapid iteration on UI design.
This seems to not be true. The flutter property editor basically allows you to just visually update the .dart source file. In the example in the page, changing the width of the Container widget to 100 in the Flutter Property Editor basically just changes the source code in main.dart to be 100. The actual running app is unaffected in any way--unless the file is saved and a hot reload is executed.
I am running Flutter 3.41.2 and my Dart is 3.11.0 and my DevTools is 2.54.1.
Expected fix
No response
Additional context
No response
I would like to fix this problem.
- I will try and fix this problem on docs.flutter.dev.