Hi Bart,
There are two defects that I believe I identified:
DEFECT #1:
- We are assuming that using a DLL is causing trouble with the IndyServer that is required for the ExternalBrowser functionallity.We will further investigate this issue as soon as we have been able to allocate sufficient development time.
No, it's not just the external browser, it's any browser. The events are not triggered (OnConnect and OnReceivedToken etc). The external browser just had the added issue of NOT triggering an event if the user terminated the webpage without authorising Dropbox.
DEFECT #2:
- Connect technique
You should be able to determine from the boolean result if the authentication worked or not.
The other issue I highlighted was that the boolean return from the AdvDropbox.Connect was not consistent. If I have a valid token saved in the INI file and I do a AdvDropbox.Connect it returns TRUE (as expected). If I do not have a valid token in an INI file or indeed if the INI file has not yet been created, EVEN IF ADVDropbox.Connect succeeds it will always return FALSE. So you cannot use the boolean property of ADVDropboxConnect to see if Authentication worked or not as you previously suggested.
ISSUE
- When ExternalBrowser is active the browser is opened through a shell execute.
This is an issue/limitation, clearly not a defect. That explains why no events are triggered by the closure of the webpage with the Dropbox Auth in it. Can you suggest what best practice might be to handle such an occurrence, a user with external browser simply closes the webpage without authorising Dropbox?Detecting when an external browser has closed is technically difficult if not impossible.
Do you put a timer in somewhere and if no (Valid) response by a certain period then timeout the process? Any suggestions?
Thx,
Kevin