>I agree that IUP should not be the solution to every problem. But in
>this case, I strongly argue that it is the correct solution because
>IUP itself already took over responsibility for the event loop. (The
>moment IupMainLoop() or IupLoopStep() were created, that ship sailed.)
IUP is an event
Ranier,
I feel like maybe your are trying to address my concern about wanting
to work on with button and not the dialog, i.e.,
// I want to do this:
IupPostMessage(my_iup_button, 42, audio_data);
// I don't want to be forced to do this
IupPostMessage(some_dialog, 42,
On 4/18/18, Ranier VF wrote:
> Hi,
> I strong believe thar PostMessage solves the request: "update gui, outside
> main thread"
> Native handles, like Windows Handle, is hidden from the user perspective.
> Therefore using in Windows driver and not using in GTK, IOS and
Hi,
I strong believe thar PostMessage solves the request: "update gui, outside
main thread"
Native handles, like Windows Handle, is hidden from the user perspective.
Therefore using in Windows driver and not using in GTK, IOS and Android
drivers, will not disturb users.
In your example, You
On 4/18/18, Eric Wing wrote:
> On 4/18/18, Andrew Robinson wrote:
>> IUP should not be the solution to every problem. It would be like
>> incorporating a cross-platform C-runtime into IUP when that is the wrong
>> approach.
And just to be clear,
Hi,
I strong believe thar PostMessage solves the request: "update gui, outside
main thread"
Native handles, like Windows Handle, is hidden from the user perspective.
Therefore using in Windows driver and not using in GTK, IOS and Android
drivers, will not disturb users.
In your example, You
On 4/18/18, Andrew Robinson wrote:
> IUP should not be the solution to every problem. It would be like
> incorporating a cross-platform C-runtime into IUP when that is the wrong
> approach. IUP is great as it is and for specialized problems it will never
> be
> able to beat a
IUP should not be the solution to every problem. It would be like
incorporating a cross-platform C-runtime into IUP when that is the wrong
approach. IUP is great as it is and for specialized problems it will never be
able to beat a mature third party app, and right now my favorite app for the
On 4/18/18, Ranier VF wrote:
> Hi,
> Obviously I'm not saying to Call PostMessage Windows function,
> in other platforms.
> So I understood, only have problem is Windows Loop Event (IUP),
> and the autor what do you cite, say clearly that PostThreadMessage
> is wrong way
On 4/18/18, Ranier VF wrote:
> Hi,
>
> "But in when using IUP, we can't just reasonably call Window's
> PostMessage because it is not cross-platform. It won't work on any
> other platform except Windows.
> This whole proposal is on how to make something like PostMessage
>
Hi,
Obviously I'm not saying to Call PostMessage Windows function,
in other platforms.
So I understood, only have problem is Windows Loop Event (IUP),
and the autor what do you cite, say clearly that PostThreadMessage
is wrong way to solve this (update GUI in another thread).
Best,
Ranier
Hi,
"But in when using IUP, we can't just reasonably call Window's
PostMessage because it is not cross-platform. It won't work on any
other platform except Windows.
This whole proposal is on how to make something like PostMessage
cross-platform."
It's OK, but in your app example, I dont see any
On Wed, Apr 18, 2018 at 1:23 AM, Jörg F. Wittenberger <
joerg.wittenber...@softeyes.net> wrote:
> Hi,
>
> just my two cents.
>
> On Apr 16 2018, Eric Wing wrote:
>
> This is a proposal to introduce a way to post and run events on the
>> main UI thread.
>>
>> Currently (as far as I know), IUP is
On 4/18/18, Ranier VF wrote:
> Hi,
>
> "This is a proposal to introduce a way to post and run events on the
> main UI thread."
>
> Just my two cents too.
>
> IUP Dialog have a WID (windows HWND). Why not use PostMessage and
> leave Windows do work?
> BOOL WINAPI
>
> It's easy to see the problem you're facing.
>
> I'm no IUP expert, however I'm pretty positive that this can be solved
> without introducing another API.
>
> In a similar situation I have been able to abstain from using the complete
> IUP abstraction around the main loop and resort to using
Hi,
"This is a proposal to introduce a way to post and run events on the
main UI thread."
Just my two cents too.
All this is related with GUI update, in another thread, other the main thread.
Then other types updates, should not interfere with IUP.
IUP Dialog have a WID (windows HWND). Why not
Hi,
"This is a proposal to introduce a way to post and run events on the
main UI thread."
Just my two cents too.
All this is related with GUI update, in another thread, other the main thread.
Then other types updates, should not interfere with IUP.
IUP Dialog have a WID (windows HWND). Why not
Hi,
just my two cents.
On Apr 16 2018, Eric Wing wrote:
This is a proposal to introduce a way to post and run events on the
main UI thread.
Currently (as far as I know), IUP is hands-off on threads.
...
It's easy to see the problem you're facing.
I'm no IUP expert, however I'm pretty
18 matches
Mail list logo