Thanks, Alex, but spending time optimizing this kludge just isn't worth the effort with my current backlog. Just wish there was a better way, a correct way.
I could log a feature request on Adobe, but it would never get enough votes. Just seems a no-brainer that the AIR runtime should fire a MOUSE_UP event to the stage when the user releases the mouse while dragging the chrome, or allow accessing the chrome from the app and adding event listeners. Seems simple enough. They do it already for resize, why not mouse up? Thanks. Erik On Oct 16, 2018, at 10:07 AM, Alex Harui <aha...@adobe.com.INVALID> wrote: Erik, Did you also ask on the Adobe forums? I'm not sure that AIR will give you mouse events when the mouse is interacting with the "chrome" of a Window. IOW, I don't think the mouse ever touched the pixels that represent the SWF content. You could write a test to see if the resize event interval is dependent on how long it takes for your app to respond to a resize event. Create a HelloWorld app that will redraw very quickly and see if you get resize events more often. If AIR can deliver resize events at, say 50ms in a simple app, then you can consider making changes to your app to respond to resize more quickly. You can use the performance profilers to see if there are bottlenecks responding to resize. You can also consider deferring certain kinds of work via callLater. HTH, -Alex On 10/16/18, 9:53 AM, "Erik Thomas" <erikjtho...@icloud.com <mailto:erikjtho...@icloud.com>> wrote: Yeah, I figured I'd have to use a timer kludge like in the SO thread. Just one more of those things about AIR that annoys me. I've implemented that pattern and it's working, though the resize events fire at roughly 200ms intervals during a drag. A 50ms timer interval suggested in SO of course couldn't work. I had to implement a 300ms timer interval to be reliably notified only after the resizing process ends with the user releasing the mouse capture. But it should be possible to get the mouse up event after the resize. That should be considered a bug in AIR, IMO. The timer kludge results in delaying a REST API call for 300ms from the last resize event is received, making the app appear noticeably unresponsive. Thanks for your response, Kyle. I guess I'll just have to live with it. Cheers Erik On Oct 15, 2018, at 3:33 PM, kamcknig <kamck...@gmail.com> wrote: As far as I know there isn't a way, a stackoverflow user asked the same https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fstackoverflow.com%2Fquestions%2F11014968%2Fdetect-when-the-resize-event-has-finished&data=02%7C01%7Caharui%40adobe.com%7C24b8a1c31a414de69b1d08d63387ea45%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753056182036471&sdata=w9Z9HLrbWsUyUDBHraKSKuqerX1O%2FLoYBqbpFLslMNE%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=https://stackoverflow.com/questions/11014968/detect-when-the-resize-event-has-finished&data=02|01|aha...@adobe.com|24b8a1c31a414de69b1d08d63387ea45|fa7b1b5a7b34438794aed2c178decee1|0|0|636753056182036471&sdata=w9Z9HLrbWsUyUDBHraKSKuqerX1O/LoYBqbpFLslMNE=&reserved=0> I can't think of any way to do so. Kyle -- Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C24b8a1c31a414de69b1d08d63387ea45%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753056182036471&sdata=sD%2FloMMx%2BfXptvCzlcPFR%2B5imOqL%2BKR6o5WjeU7SWUk%3D&reserved=0 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-flex-users.2333346.n4.nabble.com%2F&data=02%7C01%7Caharui%40adobe.com%7C24b8a1c31a414de69b1d08d63387ea45%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636753056182036471&sdata=sD%2FloMMx%2BfXptvCzlcPFR%2B5imOqL%2BKR6o5WjeU7SWUk%3D&reserved=0>
