ControlBar hide on panel_login

[edufi]

Hi, I have a controlbar under my panel navigator but I want to hide that controlbar when the panel_login is displayed. Does anyone have a suggestion on how to hide the cotrolbar for the panel login?

[Russell Craycraft]

If you can show an image of your screens, and an image of your controls I may be able to help.

I also built my own app login/main control that I could show/give you if you want as well. I use a "Main" UX that houses my entire app, minus the login screen. The login component should be a separate component, and use the "Web Security" settings to move to your main UX onLogin, and then when it times out, it will log you out, and go directly to the login screen. Keeps all of the coding out of it, and at least for me, reduces breakpoints.

*The control bar just runs a JavaScript action to open each UX in the PNL_MAIN panelcard, and keeps everything light and fast. I keep all of my UXs as small as possible, and use SQL to compute most of my stuff in a view on the backend.

image.png

[edufi]

Thanks for the information. I dont quite understand. I have my controlBar layouts named the same as my Panel Cards. I use a different layout for each panel card. My PANEL_LOGIN layout has just a html space and nothing else (would love to turn it off completely but would settle for the space) Under controlBar properties for Javascript set active layout I have the following js
var panelID = {dialog.object}.panelGetActive()
return panelID;

In the Actions I have the following JS too:

{dialog.object}.panelSetActive('NAMEQUESTION',true);
//get a pointer to controlBar
var cbObj = {dialog.object}.getControl('CONTROLBAR_3')
//refresh the controlBar
setTimeout(function(){cbObj.refresh()},0);


I think what is happening is that the controlBAr doesnt know that its on the Panel_Login when it renders. I have added the panel.SetActive code in some of both server-side and client-side events but it doesnt seem to choose the panel_login layout.

controlBar.png

[Russell Craycraft]

I added a component.
Try some of this out, and see if any of it works for you. If not, let me know.

[Russell Craycraft]

This is pretty much it. All of the code is in each button.

image.png

[edufi]

This is brilliant! Thank you. Exactly what I needed.

[Russell Craycraft]

Happy to help.

[CharlesParker]

*The control bar just runs a JavaScript action to open each UX in the PNL_MAIN panelcard, and keeps everything light and fast. I keep all of my UXs as small as possible, and use SQL to compute most of my stuff in a view on the backend.

When I first started out I did everything the hard way then I realized exactly what you have - use views, keep it light, and keep it simple!
I am slowly, re-working my entire application based on this exact roadmap - perfect!

[CharlesParker]

nice work on the tricks component but I am taking away cool points for using that legacy grey style, lol. Also reading over my last post I admit I still do everything the hard way first - mostly because right or wrong it gets easier over time to do about everything...