#Simple Reactive UI Library (Quark)

1 messages · Page 3 of 1

rain lagoon
#

using a State() that contains the identifier of the menu

#

and you make a computed state that just disables Visible

#

kinda like a stata manager for UI

digital shale
#

Different menus that can be opened

rain lagoon
#

Since you can require the module from any script

#

and it keeps it's data

digital shale
#

A managing module does make sense, it’s simple

cursive ginkgo
#

@rain lagoon ayo

#

im currently making html to quark

#

its not good yet ofc

#

but i have hopes

rain lagoon
#

lol

#

are you using AutomaticSize

cursive ginkgo
#

i was trying out a lot of stuff

#

this just the latest thing i tried

#

@rain lagoon how about you add a gradient property to stylesheets

rain lagoon
digital shale
#

i lean toward service

digital shale
rain lagoon
#

You can try that

digital shale
#

got a reuseable wheel component now

rain lagoon
#

Are you using imagelabels

digital shale
#

also the .connect() doesnt have the second paramater

#

which is the old value

rain lagoon
#

It doesn't?

digital shale
rain lagoon
#

Change the thing in Quark.Types

#

And if u want change it on GitHub and PR

digital shale
#

son

#

yeah i cant find the type

digital shale
#

@rain lagoon

if i wanted to have each wheel slice point to a tool instance id.
Is it good practice to store that data in the UI Module, or in the inventory Module, or both?

like

Weapon_Wheel_UI.Slice1 = 'ashdjhasd'

or

Inventory.Weapon_Wheel.Slice1 = 'asdasdas'

rain lagoon
digital shale
#

changes with ur inventory

#

this is meant to be like a hotbar

rain lagoon