During this meeting, the State Changers discussed issues related to FlutterFlow. They helped another participant called Cameron in understanding how to better implement a function in FlutterFlow, involving the 'addListener' logic and interaction with the 'main.dart' file.
In the process of debugging, they discovered that the 'addListener' didn't know about 'state,' which led to more explorations and trials using 'context'. They explored different options, such as using '_router' directly on line 81 but had issues with the capitalization implying it as a type. Ultimately, the team decided to proceed with a more experimental approach, encouraging the use of print statements to see what data's coming through to make more informed decisions, accepting that there will be some trial and error in getting the right solution. Additionally, they discussed the dependency and interaction between 'main.dart' and 'nav.dart' and how editing the 'main.dart' file is a 'safer' option than modifying 'nav.dart'. Finally, it's important to note that they agreed to continue exploring solutions in future meetings, emphasizing the iterative and exploratory nature of software development. The overall theme of the meeting was problem-solving, collaboration, and edification in software development using FlutterFlow.
(Source: State Change Office Hours 9/28/2023 AM )
