ok - so I was doing something dumb - #id does work

👍

One more thing if I may. I'm having trouble with it finding the separate css file. I have updated module.xml with

<themes>
        <default>
            <style resource="assets/ui/ui.css" />
        </default>
    </themes>

And my ui.css is in

Assets/ui/ui.css

and in project.xml Assets is present renamed to assets. I've tried with assets/ui/ui.css and Assets/ui/ui.css. Any ideas ?

@hallowed-ocean-84954 Hmm , maybe you should do add in the module somewhere

<resources>
        <resource path="Assets" prefix="assets" />
    </resources>

yeah tried that - and variations of it - still not reading it

is it relative to the module.xml file ?

Good question. I don't know

maybe if I move the module.xml to the same dir as project.xml is in

Checking one of my project, I don't think so. It isn't relative to where the module.xml is

ok

and moving the file has other consequences

Here is what I used it in one of my project

<resources>
        <resource path="assets/locale" prefix="locale" />
        <resource path="assets/styles" prefix="style" />
    </resources>
    <themes>
        <default>
            <style resource="style/custom.css" />
        </default>
    </themes>
</module>

very like mine

but mine is in my Source folder and my Assets folder is peer of Source

but it's relative to the project.xml dir then it should be fine. The problem I have when moving it is my components package refs don't work any more

unless there is a way to specify the source path

I cannot find a schema for the module.xml

I'm not sure what it does , but you could try compiling with "-D resource_resolution_verbose"

oh interesting - might give that a shot

oh hang on - looks like it's working

let me check

groan ! looks like vscode caching is getting in the way of updates to the file

build from command line picks up changes - restarting vsc also does

I've been having some issues with that lately

I'm glad I always build from command line ( because I was too lazy/ unintelligent to figure how to do it the vs way)

yep - it has it's benefits for sure - at least it's clearer what's going on

regardless - thanx for all your help this morning

You're welcome 🙂

Ok got it going. I have a reference library component now that provides documentation of what chapters in DeVries are related to which part of the demo. I haven't quite wired up the auto selection but manual works fine. Now I made the dropdown by pilfering approach and examples from the Dropdowns demo. I noticed a couple of things on the way past. 1. how like supported is this approach ? It for example requires an @:access to override getComponent(). Oh this is where there is a comment about how the api could be simpler. Which makes me think this might be aimed at public use. 2. If you try to interact with the UI elements before the DropDownBuilder has registered the handler then you crash during initialization. I don't know if this is intentional or not ?

couple of snaps of how it looks. Closed and open. Note the dropdown bar (?) text is updated based on which item in the listview is selected. Plan is to drive that off the configuration menu selection at the right so that the current selection when you open the lib is related to the app context.