How to make a centered label with Icon?

pspeed · February 4, 2019, 8:58pm

What is blackColor? What is fontFQ26?

…usually what I’d do to debug this is comment attributes out to see what’s causing the issue.

Pesegato · February 5, 2019, 10:11am

The issue is the background. If I remove it, then the label is drawn as specified; otherwise the Label is not visible.

Maybe the background is drawn on top of the Label?

pspeed · February 5, 2019, 10:19am

That would depend on how the background is defined… which I also can’t see.

Pesegato · February 5, 2019, 10:32am

def defPinkBackground = TbtQuadBackgroundComponent.create(
texture( name:"Interface/ui-menu-button-pink.png",
        generateMips:false ),
        1f, 50, 0, 100, 68,
        0f, false);

pspeed · February 5, 2019, 12:16pm

Try giving it an offset other than 0. It’s probably sitting right at the exact same Z… but still I’d expect the text to sort on top.

I think the glass style uses some Tbt quad components if you want to see some working examples.

Pesegato · February 5, 2019, 1:06pm

Indeed that solved my issue!

def defPinkBackground = TbtQuadBackgroundComponent.create(
texture( name:"Interface/ui-menu-button-pink.png",
        generateMips:false ),
        1f, 50, 0, 100, 68,
        1f, false);

Wait, isn’t it now on top of Label? Oh well…

Now to the next issue: Container is good for layout, but also takes over the Focus management. I’d like to use bigbanana 4-way navigation; is there a way to tell Container to not manage the focus?

pspeed · February 5, 2019, 8:45pm

a) I’m pretty sure there is a way to replace the focus root behavior but I don’t remember exactly what off the top of my head. (no time to look at the moment)

b) what does 4 way navigation mean in a vertical stack of buttons?

mitm · February 6, 2019, 5:24am

Looking forward to this one. Please post findings.

I have an issue where the container (at least I suspect that to be it) grabs focus when using arrow keys.

pspeed · February 6, 2019, 7:06am

If you don’t want any focus management at all then you can just shut it off by deactivating the function group:

github.com

jMonkeyEngine-Contributions/Lemur/blob/master/src/main/java/com/simsilica/lemur/focus/FocusNavigationFunctions.java#L54


      
          import com.simsilica.lemur.input.InputState;

          

          /**

           *  Defines the standard functions and default mappings

           *  used for UI navigation.

           *

           *  @author    Paul Speed

           */

          public class FocusNavigationFunctions {

          

              public static final String UI_NAV = "UI Navigation";

           

              public static final FunctionId F_NEXT = new FunctionId(UI_NAV, "Next");   

              public static final FunctionId F_PREV = new FunctionId(UI_NAV, "Previous");   

              public static final FunctionId F_X_AXIS = new FunctionId(UI_NAV, "X Axis");    

              public static final FunctionId F_Y_AXIS = new FunctionId(UI_NAV, "Y Axis");    

              public static final FunctionId F_ACTIVATE = new FunctionId(UI_NAV, "Activate");           

              

              public static void initializeDefaultMappings( InputMapper inputMapper ) {

           

                  if( !inputMapper.hasMappings(F_NEXT) ) {

Pesegato · February 6, 2019, 8:01am

It does matter for table-like layout, like this:

<save slot 1>  <delete>
<save slot 2>  <delete>
<save slot 3>  <delete>
<back to main menu>

mitm · February 6, 2019, 3:36pm

Thank you. Fixed.

Pesegato · February 7, 2019, 11:03am

In order to 4-way navigation to work with pre-existing component, it is necessary to add to them a Control which implements BBFocusTarget

github.com

Pesegato/BigBanana/blob/master/src/main/java/com/pesegato/bigbanana/BBFocusTarget.java

/*
 * To change this license header, choose License Headers in Project Properties.
 * To change this template file, choose Tools | Templates
 * and open the template in the editor.
 */
package com.pesegato.bigbanana;

import com.jme3.renderer.RenderManager;
import com.jme3.renderer.ViewPort;
import com.jme3.scene.control.AbstractControl;
import com.simsilica.lemur.GuiGlobals;
import com.simsilica.lemur.focus.FocusNavigationFunctions;
import com.simsilica.lemur.focus.FocusTarget;
import com.simsilica.lemur.input.StateFunctionListener;

/**
 *
 * @author Pesegato
 */
public abstract class BBFocusTarget extends AbstractControl implements FocusTarget, StateFunctionListener {

This file has been truncated. show original

The methods to implement are onFocusGain() and onFocusLost(). These method should update the status and the visuals of the Component so that it receive and lose focus respectively. Is there a way to do something like Button.receiveFocus()?

pspeed · February 7, 2019, 11:48am

You mean like this:

github.com

jMonkeyEngine-Contributions/Lemur/blob/master/src/main/java/com/simsilica/lemur/GuiGlobals.java#L373


 *  Creates a color from the specified RGBA values as if they were in SRGB space,
 *  depending on whether gamma correction is enabled or disabled.  If there is no
 *  gamma correction then the RGBA values are interpretted literally.  If gamma
 *  correction is enabled then the values are converted to linear space before
 *  returning.  
 */     
public ColorRGBA srgbaColor( float r, float g, float b, float a ) {
    if( gammaEnabled ) {
        // Note: unlike JME's seAsSrgb() method, when converting from SRGB
        //   space this method will also convert the alpha as it seems to matter in color
        //   matching.
        // ...except it didn't always work.  
        //return new ColorRGBA().setAsSrgb(r, g, b, (float)Math.pow(a, GAMMA));
        return new ColorRGBA().setAsSrgb(r, g, b, a); 
    } else {
        return new ColorRGBA(r, g, b, a);
    }
}
/**
 *  Creates a color from the specified RGBA values as if they were in SRGB space,

Pesegato · February 7, 2019, 1:30pm

Is it possible to define an alternate style for “disabled” look?

Pesegato · February 8, 2019, 7:43am

…

pspeed · February 8, 2019, 7:48am

The built in GUI elements don’t really have a concept of “disabled”, I guess.

I’ve faked it before by adding a component to the element that I wanted to disable. This component was essentially a semi-transparent gray box that swallowed mouse events… offset in such a way that it was on top of the rest of the GUI element.

To be honest, if I ever add “official” support then it would probably also be something like that.

Pesegato · February 11, 2019, 2:48pm

I ended up with this

public class AButton extends ActionButton {

    public AButton(Action action) {
        super(action);
    }

    @Override
    public void setEnabled(boolean enabled) {
        super.setEnabled(enabled);
        ColorRGBA c = ColorRGBA.Gray;
        if (enabled) {
            c = getColor();
        }
        setColor(c);
        ((TbtQuadBackgroundComponent) getBackground()).setColor(c);
    }
}

To make it work properly, I’d need to read the color I’ve defined on the groovy. How can I do that?

Also the highlight background won’t respect this. Is there a way from groovy to reference the code written here?

Pesegato · February 12, 2019, 9:19am

pspeed · February 12, 2019, 9:46am

The real issue is that enabled/disabled was not added as button actions. So probably any option you have will be a bit of a hack until that’s supported.

You can’t “read the color from groovy” but you could potentially “let groovy set it for you” by defining an actual property on AButton and marking it with the StyleAttribute annotation.

I thought about this a few different ways but I’m still not sure what you are trying to ask.

Is the button being highlighted even when it’s disabled? Is that your code doing it or mine?

pspeed · February 12, 2019, 9:48am

Button.java looks like it (correctly) won’t even call highlight on or off if the button is disabled:

github.com

jMonkeyEngine-Contributions/Lemur/blob/master/src/main/java/com/simsilica/lemur/Button.java#L436


//super.mouseButtonEvent(event, target, capture);
if( !isEnabled() )
    return;                                            
if( event.isPressed() ) {
    setPressed(event.isPressed());
} else if( isPressed() ) {
    // Only run the up processing if we were already pressed
    // This also handles the case where we weren't enabled before
    // but are now, etc.
    
    if( target == capture ) {
        // Then we are still over the button and we should run the
        // click
        runClick();
    }
    // If we run the up without checking properly then we
    // potentially get up events with no down event.  This messes
    // up listeners that are (correctly) expecting an up for every
    // down and no ups without downs.
    // So, any time the capture is us then we will run, else not