I'm using a Nested Navigation in my home screen. I'm currently having an issue with the creation of the beamers keys which affect the bevior of the digitial keyboward. As this stackoverflow post suggests, this keys are restarting themselves, making it the keyboard to behave the following way:
This is happening in all inputs inside my home view, which are quite some. Some of the solutions in that stackoverflow posts suggests to create the beamer key as static or/and place it the state of a statefulwidget (which is undesired to me but if it's required i would take the solution), this solves the issue of the beamerkey recreating itself and keyboard is fixed as well:
However, as you can see, the beamer key looses it state and route information. I tried to follow this beamer example but I hit this wall.
Notes:
As I'm currently working with BLOC pattern you will se cubits related stuff, and also stuff missing from the example as I was not sure if their were required with bloc, an example of this is @dispose and @initState methods
Each of this has it's own cubit and state in a separate class/file (cubits are classes that handles all ui events logic and emit a new state to the ui).
There are more beamer keys created inside ManagementLocation
Here's my Home Page:
class MobileHomeView extends StatelessWidget {
MobileHomeView(
{Key? key, required this.userRole, required this.routeInformation})
: super(key: key);
final UserRole userRole;
final RouteInformation routeInformation;
static final GlobalKey<ScaffoldState> _scaffoldKey =
GlobalKey<ScaffoldState>();
//This solves the issue, but beamkey looses it's rpute information
static final beamerKey = GlobalKey<BeamerState>();
Maintains route information but key keeps recreating. It's the same if I move the key inside the build method
// final beamerKey = GlobalKey<BeamerState>();
@override
Widget build(BuildContext context) {
return Scaffold(
key: _scaffoldKey,
endDrawer: HomeDrawer(homeContext: context),
appBar: AppBar(
title: Row(
children: [
Image.asset(
'assets/images/IconMoyaIntro.png',
width: 40,
height: 40,
),
const SizedBox(
width: 12,
),
const Text('Mercaditos', style: TextStyle(fontSize: 20)),
],
),
centerTitle: true,
backgroundColor: Theme.of(context).primaryColor,
actions: [
context.watch<AppBloc>().state.userDocument!.profilePicUrl!.isEmpty
? Padding(
padding: const EdgeInsets.all(8.0),
child: InkWell(
onTap: () {
_scaffoldKey.currentState!.openEndDrawer();
},
child: const CircleAvatar(
foregroundImage: AssetImage("assets/userIcon.png")),
),
)
: Padding(
padding: const EdgeInsets.all(8.0),
child: InkWell(
onTap: () {
_scaffoldKey.currentState!.openEndDrawer();
},
child: CircleAvatar(
foregroundImage: NetworkImage(
'${context.watch<AppBloc>().state.userDocument!.profilePicUrl}')),
),
),
const SizedBox(
width: 10,
),
],
elevation: 0),
body: Beamer(
key: beamerKey,
routerDelegate: BeamerDelegate(
locationBuilder: (routeInformation, _) {
switch (userRole) {
case UserRole.cashier:
if (routeInformation.location!.contains('history')) {
return CashierHistoryLocation(routeInformation);
}
if (routeInformation.location!.contains('orders')) {
return CashierOrdersLocation(routeInformation);
}
return CatalogLocation(routeInformation);
default:
if (routeInformation.location!.contains('tickets')) {
return TicketsLocation(routeInformation);
}
if (routeInformation.location!.contains('movements')) {
return MovementsLocation(routeInformation);
}
if (routeInformation.location!.contains('orders')) {
return OrdersLocation(routeInformation);
}
return ManagementLocation(routeInformation);
}
},
),
),
bottomNavigationBar: MobileHomeNavigationBar(
location: routeInformation.location!,
beamerKey: beamerKey,
homeContext: context, // este context no se pasa
userRole: userRole,
),
);
}
}
I'm using a
Nested Navigationin my home screen. I'm currently having an issue with the creation of the beamers keys which affect the bevior of the digitial keyboward. As this stackoverflow post suggests, this keys are restarting themselves, making it the keyboard to behave the following way:https://github.com/slovnicki/beamer/assets/96405082/90fdaaba-03c3-447b-b3cb-b0ef1b94791f
This is happening in all inputs inside my home view, which are quite some. Some of the solutions in that stackoverflow posts suggests to create the beamer key as
staticor/and place it the state of a statefulwidget (which is undesired to me but if it's required i would take the solution), this solves the issue of the beamerkey recreating itself and keyboard is fixed as well:https://github.com/slovnicki/beamer/assets/96405082/184498f1-ece8-4b0d-a697-565d9bc0f5b2
However, as you can see, the beamer key looses it state and route information. I tried to follow this beamer example but I hit this wall.
Notes:
As I'm currently working with BLOC pattern you will se cubits related stuff, and also stuff missing from the example as I was not sure if their were required with bloc, an example of this is @dispose and @initState methods
Each of this has it's own cubit and state in a separate class/file (cubits are classes that handles all ui events logic and emit a new state to the ui).
There are more beamer keys created inside
ManagementLocationHere's my Home Page:
In case needed, the bottom sheet form: