https://linen.dev logo
Join Discord
Powered by
# haxe-ui
  • b
    it is possible, the flash tests in the official haxe repo start up gui windows
  • b
    as long as it doesn't cause the process to hang
  • b
    on linux it requires some packages
  • b
    as long as the tests don't require any real user interaction
  • b
    i actually wonder if you could further "fake" mouse input without actually having real user input by something like "findComponentesUnderPoint(x, y)" and then just send the mouse even to the first item in that list... that should fix the "component over the top of another" one... ... i think
  • l
    it might work, but it depends on what x and y you use. what if only half of a button is covered and you happen to take a point from that half?
  • b
    true, but the same would apply if you were actually simulating mouse input, i mean, with my system i took the center point of the component and made windows "click" there, but if the, say, button, was 1/3rd obscured then it would have been fine...
  • b
    i mean, i guess you could as part of start up or something make sure no interactive components are overlapping... ... i mean, i think there would never be a good reason for them to
  • l
    it's probably also beyond the scope of automated UI tests to figure out whether an occlusion is valid or not. in the end it's an addition to manual testing. so taking the center and sending events to whatever is on top of it should work out. and if tests sometimes fail because of overlapping elements then a human has to investigate. it would be nice to have a screenshot of the app at time of failure, but I don't know if that's doable.
  • h
    A screenshot is doable. I do it in an automated test for my shader lib. I only have one example but I have a capture class that works for a flixel spritewhich captures the bitmap data. So it might well be backend specific but it can be done
  • b
    i beleve i found a bug with dropdowns
  • b
    lets say i have adropdown with 3 items - each item wider then the other
  • b
    when selecting the shorter options, things look corrupted
  • b
    dropdowns autosize by default, meaning the width with be the width of the content, which changes depending on string size. You can either give the drop down a px or % width, or use "dropDownWidth" to give the list a fixed width
  • b
    👍
  • p
    In my tableviews row I have a button to remove the associated row from the datasource. The renderer knows its row data but it doesnt know the datasource? Not sure how to pass it a link top datasource?
  • p
    essentially make the X button delete the appropriate row https://www.haxeui.org/builder/?hqsmjb
  • p
    well... on the button custom renderer I went with onclick cast(this.parentComponent.parentComponent.parentComponent, TableView).dataSource.remove(data);
  • r
    I have a css file attached in my main layout XML, and it seems to work fine, except it seems like it is being cached or something. It does not always show my latest changes when I compile. Is there are way around this?
  • b
    could this be an openfl thing? Im assuming openfl as i think ive seen it before there
  • b
    about the color picker - is the color picker open source? if so, can you send a link (@bright-gpu-74537)
  • b
    it will be in core, yeah, but its not yet as i need to take it out of my test project (where its a custom component) and put actually put it into core, and move the styles about etc
  • r
    I remember seeing an example XML layout where there was a single view, but a content area would be switched out for something else. Does anyone know what I am talking about? Or maybe there was just a few elements, but only one was enabled at a time.
  • b
    im not 100% sure what component you mean tbh... if it was a self contained component then you'll likely find it in the component explorer: http://haxeui.org/explorer/ That has (i think) every component in haxeui (and some variants), but if it was an app view, then it probably wont help much
  • b
    hmmm, not ideal... btw you could also do: 
    this.findAncestor(TableView).dataSource.remove(data)
  • b
    i think it would be nicer though if the item renderer "magically" got a reference to the IDataComponent (which in this case would be the tableview), ill have a look
  • p
    much nicer than parent drilling
  • b
    yeah, you dont need a cast or anything either... though i still think it would be nice to able to do something like 
    this.dataComponent.dataSource
    or even 
    this.dataSource
    (though the latter might be a little misleading)
  • p
    I like this.datasource but you may be correct, it could be misleading. It makes sense to have data and datasource to me. But im in the weeds already
  • b
    yeah, i just think that "datasource" makes it seem like its a data source for this renderer... maybe "parentDataSource" or something? Dunno
1...119111921193...1687Latest