https://linen.dev logo
Powered by
# haxe-ui
  • m
    Spot on
  • b
    (it works fine if you comment them out btw, but its not correct to)
  • b
    oh, and looking at the errors its super simple fixes too... cool
  • m
    That's great... I supposed from the fact that mouse stuff was not conditionally compiled, that there was no code for handling touches, so I didn't even try commenting them out
  • b
    well, its basically this:
  • b
    Copy code
    haxe
    private static var buttonPressed(get, null):Int;
    private static function get_buttonPressed():Int {
        var n = -1;
        if (FlxG.mouse.pressed == true) {
            n = 0;
        } else if (FlxG.mouse.pressedRight == true) {
            n = 1;
        }
        return n;
    }
  • b
    and
  • b
    Copy code
    haxe
        if (Toolkit.backendProperties.exists("haxe.ui.flixel.mouse.useSystemCursor")) {
            FlxG.mouse.useSystemCursor = Toolkit.backendProperties.getPropBool("haxe.ui.flixel.mouse.useSystemCursor");
        }
  • b
    neither of which are relevant on mobile... so i can just #if def them
  • b
    no biggie, but i want to make the UI scale correctly first ofc, those fixes are 10 second fixes
  • m
    Awesome, I saw your question in the flixel forum, and yeah, I think there's a property in FlxSprite that is basically the anchor for transformations
  • m
    I don't remember the name of the property though, but if I recall correctly it's calculated to be in the middle of the sprite by default
  • m
    Copy code
    WARNING: The origin of the sprite will default to its center. If you change this, the visuals and the collisions will likely be pretty out-of-sync if you do any rotation.
  • b
    yeah, worked it out... its .origin... i did try that, but it wasnt working, but that was because i was scaling the sprite before creating the graphic
  • m
    So I commented the project.xml lines and built it here, worked fine 🙂
  • b
    getting there 🙂
  • o
    Ian have improved the Quad drawing ( with triangles ) control quite a bit. Just working on a simple hacky shift calendar ( sorry colors terrible ), and still to setup shift coloring. Basically it takes a png in, you draw the quads above the image shapes and then just move them to location you need. The dates are scaled, the months not. Tints can be applied to the quads.
  • o
    Obviously can use colors over textures and complex shapes but hopefully improving the texture quad support to make it more useable.
  • o
    once I get the 4x4 day stuff rendering properly I will upload the demo code. But be interested in seeing how far it's is away now from being targetted by haxeui.
  • o
    4x4 is for practical planning. The tinting has not worked as well as I hoped, and colors terrible, but can tweak later.
  • b
    if the api is pretty straight forward it should be fairly simple to create a new backend... but its not something ill be able to do, at least not for a while, ive got waaaaay to many things on the go (i can ofc advise 🙂 )
  • o
    depending on if your using a texture or color pen. When using texture the rectangles map to the actual texture. For instance this helper. If drawing with texture you then normally change the position and size ( as you saw I have used that for 9-slice experiments ).
    Copy code
    haxe
quadShaper.xy = { x: x, y: y };
quadShaper.dim( w, h );
  • o
    so add the quad over the image location, then change xy to required position.
  • o
    I don't know if that is making much sense. The basic ideas is that with a pen you draw your shapes to an array and then at render time you decide which parts of the array to render by index ranges.
  • o
    the arrays have abstracts so you only deal with triangle indexes not the lower level array entries.
  • o
    So for instance this is fairly basic drawing example. So you can see it here But for api you probably would not use much of the drawing stuff.
  • b
    i mean, that drawBox looks pretty straight forward, but as i mentioned, i simply dont have time to create/maintain another backend... esp. one that sounds like its an experiment more than anything else
  • o
    Well trilateral3 does work with gluon or lime, not yet tried wiring up images yet. But in theory this example would work in gluon c++ and may well run fairly fast in lime as it does not have as much overhead just two sets of shaders ( color or texture ).
  • o
    Some issues to resolve with mousing and subpixel scaling, and needs more stuff added to allow drawing to frames. Font support is very limited you can draw the odd title with ttf font engine or you can use an atlass.
  • o
    Really need to improve atlas stuff for fonts.
1...593594595...1687Latest