Hi,

been thinking about this for a while:

It actually is correct that the frontend becomes irrepsonsive
when the backend does a re-connect or re-scan.

When a re-connect or re-scan is performed, the old information
presented in the frontend is outdated, and the user should not
click around on it anyway.

As i see it, all that was needed was something like this
(the missing steps are marked with a *):

1. User hits connect or re-scan button.
2. * GUI goes in state "currently locked, rescanning"
    (or "reconnecting") where the interactive GUI elements
    are greyed out and this message is shown.
3. GUI calls back-end process.
4. GUI waits until backend process terminates.
5. GUI rebuilds it's list entires and status.
6. * GUI unlocks itself, user can chose from new data.

No need for GUI multithreading, everything is consistent.

Kind regards,
T.


On 08/31/2015 02:22 PM, Edward Bartolo wrote:
> Hi Aitor,
>
> Please, wait until I give you the go ahead as I am trying to add a
> separate thread to take care of the backend. There are some bugs in
> the Lazarus' Visual Component Library that I have to bypass somehow.
>
> Edward
>
> On 31/08/2015, aitor_czr <aitor_czr@???> wrote:
>> Hi Edward,
>>
>> I will try to debianize your project. But i not promise it will be soon.
>> This week i am too busy.
>>
>> I also have two projects in my mind:
>>
>> libpqxx++ -> A migration to C++ of some features of libpqxx
>> (postgresql)
>> libhpdf++ -> A migration to C++ of some features of libhpdf (Haru)
>> with UTF-8 support
>>
>> I'm not sure if the names are right, because they collect only some
>> features of the C libraries.
>>
>> Both are started.
>>
>> Aitor.
>>
>> On 31/08/15 09:43, Edward Bartolo <edbarx@???> wrote:
>>> I am attaching my updated code to this email as I couldn't commit my
>>> changes. GIT is blocking me.
>>>
>>>
>>> Edward
>>
>>
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
>