| [10-05 21:51] | [Chat] | Icewolfz: but if enabled and you get the refuse error it should still cause the auto connect system to trigger |
| [10-05 21:51] | [Chat] | Icewolfz: instead of not triggering like it does now |
| [10-05 21:52] | [Chat] | Icewolfz: proably ets i can do |
| [10-05 21:52] | [Chat] | Icewolfz: this way it allows the user ot contorl what happens |
| [10-05 21:52] | [Chat] | Icewolfz: but i also left it still etting teh client.errored flag |
| [10-05 21:52] | [Chat] | Icewolfz: so in throy you could also do manualy triggers and do clinet.errored |
| [10-05 21:53] | [Chat] | Alatar: sorry, need a minute |
| [10-05 21:53] | [Chat] | Icewolfz: no worries |
| [10-05 21:53] | [Chat] | Icewolfz: seems email is hating your log attachs me for something |
| [10-05 21:53] | [Chat] | Icewolfz: overall this new seting should at least allow yu to force reconnect even if it errors |
| [10-05 22:29] | [Chat] | Icewolfz: yeah the auto connect on error hsoudl fix your reconnect i think |
| [10-05 22:29] | [Chat] | Icewolfz: as the error ti self is netowrk |
| [10-05 22:29] | [Chat] | Icewolfz: just read some more info about that error and it abislyc something in the middle blockign the connection for what eve rreason |
| [10-05 22:29] | [Chat] | Icewolfz: and the new setting i created hsould allow oyu to keep connecting instead of just stopping liketi does not |
| [10-05 22:30] | [Chat] | Icewolfz: at least if i got the logic test right ;P |
| [10-05 22:33] | [Chat] | Alatar: I just pulled it and rebuilt on windows. |
| [10-05 22:34] | [Chat] | Icewolfz: hopfully that new setting fixes your issue |
| [10-05 22:34] | [Chat] | Icewolfz: its the best i can do |
| [10-05 22:34] | [Chat] | Roku: I'll rebuild on linux now |
| [10-05 22:34] | [Chat] | Icewolfz: the setting at least lets you controll the auto connect more if nothing else |
|
| Back to List |
