Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 956315
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 16, 20262026-05-16T00:31:19+00:00 2026-05-16T00:31:19+00:00

I’m creating a pretty simple form, and I’m running into an issue with Controls/components

  • 0

I’m creating a pretty simple form, and I’m running into an issue with Controls/components shifting position (textboxes and checkboxes in particular) by a few pixels upon selection. It’s by no means breaking my interface, but you can imagine it’s a bit of an irritant. I have a feeling it’s an issue with the custom node(s) I’ve created… though I can’t determine where the problem would be.

I did something similar before without any trouble, but ever since I tried “modularizing” my code (created a custom node with label and texbox opposed to separately declaring each in the main) I’ve come across this (along with a few other subtle issues). Here is my custom node… in case this gives way to figuring out my problem.

public class NumberWithLabelNode extends CustomNode {

public var width: Number;
public var height: Number;
public var x: Number;
public var y: Number;
public var labelText: String = "Generic Label:  ";
public var text: String = "0.0";
public var columns: Integer = 5;
public var error: Boolean = false;
public var errorText: String = "  Invalid input.";

public override function create(): Node {
    return HBox {
                width: bind width
                height: bind height
                content: [
                    Text {
                                content: bind labelText
                            },
                    TextBox {
                        layoutInfo: LayoutInfo { hgrow: Priority.NEVER }
                        columns: bind columns
                        text: bind text with inverse
                    },
                    Text {
                        visible: bind error
                        fill: Color.RED
                        content: bind errorText;
                    }
                ]
            }
}

}

If you see anything I’ve done incorrectly/doesn’t follow standards, please let me know. To re-iterate, I want this custom node to behave exactly as if I created a label and textbox in an hbox.

I’m hoping somebody can at least guide me in the direction of where my issue could be without having to look at the rest of my source (may be a long shot… I’m hoping to not have to strip down code to post here).

Thanks in advance!

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-16T00:31:19+00:00Added an answer on May 16, 2026 at 12:31 am

    I ended up getting things working more to my liking. I ended up extending both CustomNode and Resizable (and implementing the needed methods for Resizable… see API). I found this helpful -> http://blog.cedarsoft.com/2010/05/javafx-template-for-resizable-customnode/.

    Something to note: CustomNode is not a Resizable. JFXtras adds a Node called XCustomNode that adds the (missing) Resizable feature(s). The JFXtras libraries can be found at code.google.com/p/jfxtras/downloads/list (sorry… can only post 1 link right now). Stick to the 0.7 builds if you’re using JavaFX 1.3. The 0.6 versions work with JavaFX 1.2.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.