Ryan

> LMK when you want me to take a look again Will do. QTableWidget is the best (no more hard coded XML strings), but I'm spending time mucking with the...

At this point, I have done an attempt at replacing the get*Label() functions with the following: ``` RenderNavThroughWPFeedback( QTableWidget* table, const nav2_msgs::action::FollowWaypoints::Feedback msg = nav2_msgs::action::FollowWaypoints::Feedback() ); ``` There is a...

I could use some clarification on the "cleanup" behavior after actions complete. There are some spots where data is left as-is, and others where it's immediately reset to zero at...

Yea, overall that agrees with my expectations. Pushing what I have now in 68cfb2f838afa37d818b72e7110d271f55bfe9d6, which is everything is always visible. I'll go through and figure out how to use `assignProperty`...

Good news - UI is looking [less look a data table and more like the original. Rows are dynamically added fine now too.  I think found some bugs in...

PR is ready for review. I've met all the acceptance criteria. Of note, I couldn't ever figure out how to get the state machine into `running_follow_waypoints`. So either I can...

> Awesome! What about the big gap at the end of the table your last image shows? > > > In Follow WP mode, Waypoint cound does not change UNLESS...

> > Of note, I couldn't ever figure out how to get the state machine into running_follow_waypoints > > @Ryanf55 could you please explain why do you want to go...

> Yeah, I have to agree with you, the naming sounds bit confusing. Sure, I would guess Steve will also agree with your proposal. > > As Steve pointed out...

> > > Of note, I couldn't ever figure out how to get the state machine into running_follow_waypoints > > > > > > @Ryanf55 could you please explain why...