BtnCmd-DWC Plugin - Customise DWC - v01.03.05 20-09-24

Diamondback

@mintytrebor Looks like deleting and re-adding the text solved that issue.
If the empty panel + extra panel for text is the desired way of doing header, can you maybe default the layer of the panels to be at the bottom rather than the top?
Atm, when you add such a background to an existing panel, it covers everything and every single button needs to be brought to the top manually.

Diamondback

@mintytrebor said in BtnCmd-DWC Plugin-Custom Layouts & Buttons - v0.9.04 20-10-21:

@diamondback Try clicking the bring to the front button, and save. Then refresh the browser.

I tried that before, no luck. Only deleting and adding again had any effect.

MintyTrebor

@diamondback said in BtnCmd-DWC Plugin-Custom Layouts & Buttons - v0.9.04 20-10-21:

If the empty panel + extra panel for text is the desired way of doing header, can you maybe default the layer of the panels to be at the bottom rather than the top?

No.

But it should be respecting the layering order you specify. So this may be another bug in the custom panel code. I'll look into it.

Diamondback

@mintytrebor It does respect the layering, it's just that it starts out at the very top. So in my case with these buttons, I need to bring all the buttons to the front again. Not a big deal, just not ideal from a usage POV

MintyTrebor

@diamondback I'm referring to this issue you mentioned earlier...

If the text is on the top in edit panel mode it should be on the top in layout mode...
You should not need to delete and re-add it to make it display on the top.

Update : Found & fixed the bug. I'll include it on the next release, which will be in a few days.

And just to explain the 'No' to your request.

If each new button or panel is added at the bottom (lets call this layer 1), then every time a user adds a new button/panel the following actions would need to be undertaken:

Every existing button/panel on screen would have to be updated to increase its current layer by +1, before adding the new button/panel to the screen, to maintain the existing layer structure.
BtnCmd would then need to identify a blank space on the screen, large enough to accommodate the new button/panel, so that is was not rendered behind existing buttons/panels. Otherwise the user may not be able to "access" the new button/panel to move/edit/resize it. Plus, if there wasn't any free space to put the new button/panel, it would have to re-arrange all the existing buttons/panels positions automatically to create blank space, and do this whilst trying to retain the layout the user has created.

Whilst 1 is possible, 2 is not a good idea under any conditions. A send to back function may be possible, so I will look into it.

Diamondback

@mintytrebor said in BtnCmd-DWC Plugin-Custom Layouts & Buttons - v0.9.04 20-10-21:

And just to explain the 'No' to your request.

If each new button or panel is added at the bottom (lets call this layer 1), then every time a user adds a new button/panel the following actions would need to be undertaken:

Every existing button/panel on screen would have to be updated to increase its current layer by +1, before adding the new button/panel to the screen, to maintain the existing layer structure.

BtnCmd would then need to identify a blank space on the screen, large enough to accommodate the new button/panel, so that is was not rendered behind existing buttons/panels. Otherwise the user may not be able to "access" the new button/panel to move/edit/resize it. Plus, if there wasn't any free space to put the new button/panel, it would have to re-arrange all the existing buttons/panels positions automatically to create blank space, and do this whilst trying to retain the layout the user has created.

Whilst 1 is possible, 2 is not a good idea under any conditions. A send to back function may be possible, so I will look into it.

That's perfectly understandable, another button to reduce the layer would be fine as well

cosmowave

@mintytrebor It will be nice to be able to change the background color of the "standard charts" (e.g. temp chart)...
The "normal temp chart" has a light grey backcolor, in btnCmd the temp chart backcolor is black (or transparent?). For me, the standard grey one is easier readable...

MintyTrebor

@cosmowave Never noticed it, but it is the same for most of the other DWC panels - I'll look into it.

MintyTrebor

@cosmowave Published Beta 0.9.06

Changes:
Fixed Text issue in custom panels.
Fixed background colour of the Standard DWC panels to be the same as the default theme (light/dark)

cosmowave

@mintytrebor wow... that was realy fast!
Thanks. I will test it today evening.

cosmowave

@MintyTrebor It works. And for me in dark mode it's much better readable now.
Thanks!

radiomodell

This plugin is great. I modified DWC1.22 with a lot of effort to make it more suitable for CNC and Laser mode.
With this plugin I was able to nearly "rebuild" former functionality in no time. The only thing I am missing is an option to put a text(number) input to a global variable. Or did I miss something?

DWC1.22.JPG

Here is the part of a screenshot of the old DWC.

I use a standalone Duet2 Ethernet with Firmware Release 3.4.0 beta 7, Duet Web Control 3.4.0-b7 and BtnCmd-DWC Plugin v0.9.06

MintyTrebor

@radiomodell I'm glad you find it useful.

I'm currently working on Beta 0.10.01 right now to address some issues with the changes introduced in DWC 3.4b7, if I am able to add a way of setting global variables then I will do so (but no promises ).

As a workaround you may be able to use a similar approach as described here.

radiomodell

@MintyTrebor Thanks for the fast reply.

I will try the workaround. Please no extra hurry. I will be patient.

MintyTrebor

Version Beta 0.10.02 for DWC 3.4b7 has been published in my repo.

Changes:

Fixed layout mode issues in custom panels.
Added new Global Variable Input Panel - Allows you to update pre-defined Global Variables in the UI
Changed how BtnCmd works with Mobile Resolutions. BtnCmd's mobile UI now triggers at higher resolutions in line with DWC.
Removed Height Adjuster in Global Settings. - Available layout space will now be a fixed size for the device/resolution size you are using.

Please review the release notes before upgrading as there have been significant behind the scenes changes to align BtnCmd with DWC's new mobile UI changes.

Note: To use the new Global Variable input panel, the variable must already be created in the normal methods.

radiomodell

@mintytrebor You are fast! I will try new version of plugin tomorrow.

Here is my actual status that still needs some fine tuning.

I really like the flexibility given by the plugin.

radiomodell

@mintytrebor The Global Variable Input Panel works well for me.
Just replaced the Object Mode Value panel. The Input Panel works as both,display and input.
Pressing Enter transfers input to the global variable.
Configured as string input it accepts numbers also. But comas are not converted to dots as in number configuration.

Thanks for the fast modification

radiomodell

@mintytrebor I would like to add two points to the wish list after a while of testing:

Is it possible to switch to last active BtnCmd Panel after starting a job? Standard is switching to the Status panel.
Is it possible to change color of Object Model panels and Global Variable Input panels dependent on conditions? Like "HOME X" button in Dashboard. It is orange until it changes to blue when homed.

And please no hurry! It is short before Christmas.

MintyTrebor

@radiomodell @radiomodell said in BtnCmd-DWC Plugin-Custom Layouts & Buttons - v0.10.02 21-12-21:

Is it possible to switch to last active BtnCmd Panel after starting a job? Standard is switching to the Status panel.

That is standard DWC operating behaviour - even if I could change it, I'm reluctant to mess with the way DWC operates.

Changing colour might be possible for OM Panels/Inputs, but its likely to be a significant amount of work, I'll add to the wish list.

In your previous post you mentioned...

@radiomodell said in BtnCmd-DWC Plugin-Custom Layouts & Buttons - v0.10.02 21-12-21:

Configured as string input it accepts numbers also. But comas are not converted to dots as in number configuration.

I believe this is standard behaviour (I do not do any manipulation other than to check that the entered value is a Number if you have set the OM Input Panel properties to be a number). Try using the set global with and without quotes eg:

set global.#### = "1234.5"

and

set global.#### = 1234.5

Check the object model browser and you will see that the first example is shown in quotes, and the second is not. One is a string the other is a number. A number in a string, is still a string, and will not get modified.

BtnCmd uses the same command as above to set global variables. So it should behave the same way as if you were to enter it manually, or via a macro.

Forgot to add I have not yet implemented the ability to allow variables to be assigned with other object model values by reference or other expressions - I do plan to add that capability later.

Thanks for the feedback.

MintyTrebor

@radiomodell So I am thinking about the idea of a 3rd type of variable input panel - true/false (alongside String/text & Numeric)

I am not sure there is any value in adding other types. I think it works better as a quick simple entry panel for setting control parameters etc. Anything more complex can still be entered via the standard DWC console entry function, or via a macro.

Thoughts?