Re: [twsocket] ICS, FireMonkey, Android, Windows and PostMessages

2013-12-16 Thread François Piette
 Window handles do not exist in OS X too but that can be emulated as I
showed in ICSv8. 
 The nature of PostMessage() and SendMessage() is that they take a target
(call it handle).

This is what I've done. The Windows handle is the instance of
TMessagingSystem. I made PostMessage a method of the object because I like
the OOP way, but PostMessage could have been done a simple function taking
the TMessageSystem instance as first argument like a Window Handle. This
is just the same.

 Will your port introduce a new incompatible source branch as it was the
case with your Kylix port in the past? 

I don't know yet. I'm progressing slowly and carefully, building other
applications in the meanwhile. This way I get more experience with the new
Android API and will in the end produce better code. Obviously my goal is to
hide as much as possible changes.

 I already wrote an AnsiString class which does the required work.
 I saw it, that's far away from solving the problem! 

At least it solve all problem I had until now. And since it is a plain
class, IMO it is easy to solve other problems, if any.
 
 Let's see and count the memory leaks and other issues caused by ARC-ed
objects 
 over the next years in your ported ICS source code.

We'll see. Anyway we have no other choice. ARC is mandatory on Android.

 Well, zero-based strings is a complety unnecessary mess IMO.

Agreed.

-- 
francois.pie...@overbyte.be
Embarcadero MVP
http://www.overbyte.be
http://francois-piette.blogspot.com




-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be


Re: [twsocket] ICS, FireMonkey, Android, Windows and PostMessages

2013-12-16 Thread François Piette
Thanks for your favorable opinion.
You're welcome.

-- 
francois.pie...@overbyte.be
Embarcadero MVP
http://www.overbyte.be
http://francois-piette.blogspot.com





-Message d'origine-
De : TWSocket [mailto:twsocket-boun...@lists.elists.org] De la part de
Walter Bohlin
Envoyé : lundi 16 décembre 2013 00:38
À : ICS support mailing
Objet : Re: [twsocket] ICS, FireMonkey, Android, Windows and PostMessages

Francois,

You are nothing short of genius. I cannot tell you how much your ICS
components for C++ Builder have helped me complete work that I wasn't able
to do on my own. On top of that, it was an education for me, one that is far
from over, even at my advanced age.

Thank you ever so much!

Walter


On 12/15/2013 11:29 AM, François Piette wrote:
 While busy at porting ICS to Android, I had the need of replacing 
 Windows custom messages by something else which is portable across 
 Windows and Android.

   

 Something else? Not sure! Finally, I build a really small piece of 
 code which implements Windows messages on Android and on Windows.


 Of course the Windows implementation makes use of Windows own 
 messaging as usual. On Android it makes use of the looper API.



 The result is code which allows to build application 100% portable 
 between Windows and Android and yet make use of Windows custom messages.


 As you know ICS code and many samples make heavy use of Windows custom 
 messages. Problem solved!



 Read full article at:
 http://francois-piette.blogspot.be/2013/12/firemonkey-android-windows-
 and.ht
 ml
 http://www.linkedin.com/redirect?url=http%3A%2F%2Ffrancois-piette%2Eb
 logspo 
 t%2Ebe%2F2013%2F12%2Ffiremonkey-android-windows-and%2Ehtmlurlhash=7lc
 q_t=t
 racking_anet

   


--
To unsubscribe or change your settings for TWSocket mailing list please goto
http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be

-- 
To unsubscribe or change your settings for TWSocket mailing list
please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket
Visit our website at http://www.overbyte.be