Another cabin made of Norwegian pallets?

Anyone know if ImageView is supposed to set the error or exception properties if a URL isn't found?

I get an error if a class path resource isn't found but not a 404 absolute URL

Same behavior on both mac and Linux yesterday

I think that is as expected, at least in my experience.

apparently, you need the background flag set to trap the not found exception. if an image is created on a bad absolute URL, it just won't display

(without the flag)

My findings http://bekwam.blogspot.com/2017/05/javafx-image-error-handling.html

Nice, Carl! I didn't know that 🙂

I knew about the

errorProperty

and

exceptionProperty

but not about the

progressProperty

. Learning something new everyday! 🎉

@edvin maybe we could add an onComplete to an image() builder that fires when progress=100%?

that way, you don't need to wrap the ImageView / Image in a runAsync

@carlw Nice post👍

@nimakro thx. since you're a mechanical keyboard fan, you might like this one too https://fxdocs.github.io/docs/index.html#_imageview

@carlw Hehe nice is that a 40% or a 60%?

40

@alexp11223 for #342, have you tried a different concurrency object like a latch?

@User uploaded a file: Untitled

^ prints "Hi" and the exception from null!!

isn't it just catched inside thread?

you're trying to hold up program execution, right? the thread() executes, the latch holds up the program, and when the NPE is thrown, the latch is freed

i'm catching the exception because I need a place to put the countDown() after the thread is finished

yeah, but I was trying to do it without putting anything additional in the thread itself. and if exception is catched inside thread (or inside

runLater

) then there is no issues even with await. The issue is when it is not catched or if it is rethrown (in

fail

of

runAsync

or

runLater

)

This doesn't work for you? runAsync { Thread.sleep(2000) null!! } ui { println("Hi") } fail { println("Error") }

I encountered it when writing test like this:

val finishCalled = false
        val executor = SomeTaskExecutor(..., 
        onFail = {
            throw it // should fail test
        }, onFinish = {
            finishCalled = true
        })
        executor.start()

        executor.isFinishedProperty.awaitUntil()

        assertTrue(finishCalled)
        assert......

SomeTaskExecutor

starts a new thread and calls

onFail/Finish

inside

runLater

What about something like this? I don't see where you're setting the flag in the code listing posted with #342 (falseFlagProperty)

Plus these lines val finishedFlagProperty = SimpleBooleanProperty(false) var finishedFlag by finishedFlagProperty val failFlagProperty = SimpleBooleanProperty(false) var failFlag by failFlagProperty

yeah. this will work of course, and in tests even asserts after await (with rethrown exception) are executed (in normal app statements after await are not executed in this case, not sure why) but it would be much better if await did not swallow exceptions like this 🙂 (at least those that are thrown from FX thread)

what do you mean swallow exceptions? if i pull out the property.set from the thread, there's no relationship between the thread and the remaining code

I was talking about my original example code or junit test code above