from __future__ import annotations from dataclasses import KW_ONLY, field from typing import * # type: ignore import rio from .. import components as comps class Navbar(rio.Component): """ A navbar with a fixed position and responsive width. """ # Make sure the navbar will be rebuilt when the app navigates to a different # page. While Rio automatically detects state changes and rebuilds # components as needed, navigating to other pages is not considered a state # change, since it's not stored in the component. # # Instead, we can use Rio's `on_page_change` event to trigger a rebuild of # the navbar when the page changes. @rio.event.on_page_change async def on_page_change(self) -> None: # Rio comes with a function specifically for this. Whenever Rio is # unable to detect a change automatically, use this function to force a # refresh. self.office = self.session[comps.Settings].office #print(self.office) await self.force_refresh() checkpage: str = "in" office: str = "" def sub_page(self, event: rio.DropdownChangeEvent): page = event.value self.session.navigate_to("/" + page) self.checkpage = "n/a" def set_office(self, event: rio.DropdownChangeEvent): settings = self.session[comps.Settings] settings.office = event.value self.session.attach(self.session[comps.Settings]) #print(settings.office) self.office = event.value @rio.event.on_populate def set_office_init(self): self.office = self.session[comps.Settings].office print(self.office) def build(self) -> rio.Component: # Which page is currently active? This will be used to highlight the # correct navigation button. # # `active_page_instances` contains the same `rio.Page` instances that # you've passed the app during creation. Since multiple pages can be # active at a time (e.g. /foo/bar/baz), this is a list. active_page = self.session.active_page_instances[0] active_page_url_segment = active_page.page_url # The navbar should appear above all other components. This is easily # done by using a `rio.Overlay` component. return rio.Overlay( rio.Row( rio.Spacer(), # Use a card for visual separation rio.Rectangle( content=rio.Row( # Links can be used to navigate to other pages and # external URLs. You can pass either a simple string, or # another component as their content. rio.Link( rio.Button( "Browse", icon="material/info", style=( "major" if active_page_url_segment == "" else "plain" ), ), "/", ), # This spacer will take up any superfluous space, # effectively pushing the subsequent buttons to the # right. rio.Spacer(), # By sticking buttons into a `rio.Link`, we can easily # make the buttons navigate to other pages, without # having to write an event handler. Notice how there is # no Python function called when the button is clicked. rio.Dropdown( options={ "ALL": "all", "US-CHI": "us-chi", "US-SC": "us-sc", "DE-NT": "de-nt", "CN-SHA": "cn-sha", "IN-BAN": "in-ban" }, on_change=self.set_office, selected_value=self.bind().office, ), rio.Dropdown( options={ "Scan...": "n/a", "Check in": "in", "Check out": "out" }, on_change=self.sub_page, selected_value=self.bind().checkpage, ), rio.Link( rio.Button( "Add", icon="material/news", style=( "major" if active_page_url_segment == "add" else "plain" ), ), "/add", ), # Same game, different button rio.Link( rio.Button( "About", icon="material/info", style=( "major" if active_page_url_segment == "about-page" else "plain" ), ), "/about-page", ), spacing=1, margin=1, ), fill=self.session.theme.neutral_color, corner_radius=self.session.theme.corner_radius_medium, shadow_radius=0.8, shadow_color=self.session.theme.shadow_color, shadow_offset_y=0.2, ), rio.Spacer(), # Proportions are an easy way to make the navbar's size relative # to the screen. This assigns 5% to the first spacer, 90% to the # navbar, and 5% to the second spacer. proportions=(0.5, 9, 0.5), # Overlay assigns the entire screen to its child component. # Since the navbar isn't supposed to take up all space, assign # an alignment. align_y=0, margin=2, ) )