First of all, I’d like to note that a package is available to make a StatelessWidget from a function: functional_widget The gain is performance is not necessarily true. It depends on how you use your widgets, mostly how you use them to manage your state. By default, classes may degrade performances when opposed to functions … Read more
This question seems to indicate that objects are not disposed when the StatelessWidget gets destroyed, at least not immediately. In any case, when you are using a TextEditingController (or maintaining any mutable state), then you should use a StatefulWidget and keep the state in the State class. The State class has a dispose() method that … Read more
Replace onPressed: Navigator.push(…) with onPressed: () => Navigator.push(…) If you need to use await keyword, you can do onPressed: () async { await Navigator.push(…); await anyOtherMethod(); }
Yes you can do this simply by passing the info to the constructor. Something like this: class MyApp extends StatelessWidget { MyApp(this.yourData); final int yourData; @override Widget build(BuildContext context) { return new MaterialApp( title: ‘App Title’, theme: new ThemeData( primarySwatch: Colors.green, ), home: new MainBody(yourData), ); } } class MainBody extends StatelessWidget { MainBody(this.yourData); final … Read more
A StatelessWidget will never rebuild by itself (but can from external events). A StatefulWidget can. That is the golden rule. BUT any kind of widget can be repainted any times. Stateless only means that all of its properties are immutable and that the only way to change them is to create a new instance of … Read more