Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to prevent error with infopanel not disappearing. #235

Merged
merged 3 commits into from
Sep 14, 2015
Merged

Changes to prevent error with infopanel not disappearing. #235

merged 3 commits into from
Sep 14, 2015

Conversation

daryllabar
Copy link
Collaborator

Changes to prevent error with infopanel not disapearing. Don't connect, open a plugin, then attep to connect twice, before the first connection completes, two panels will be opened, and one will never close. This does not fix the issue where the XTB doesn't work correctly when connecting first.

ConnectionManager.cs

  • Had to add a Parameter to be able to pass back the Popup Message

MainForm.PluginsManagement

  • Added a chec to see if ther eis no constructor. The Tag has to be populated, or else a null ref exception will get thrown. Throw a better message earlier

Added Error Logic handler if there is a Reflection Type Load Exception.
FormHelper.cs

  • Added an overload for AskForConnection that accepts an Action that is called before the actual Async process is kicked off. This allows the message to be displayed before the actual call is made.

ConnectionParameterInfo.cs

  • Class to help define the parameters sent in the connection call

MainForm.cs

  • Removed infoPanel field, since there may be more than one open at a time.
  • Changed Parameter to be the info parameter
  • Changed the infoPanel to be set wihtin the ConnectUponApproval call

Sync From Original to My Fork
…t, open a plugin, then attep to connect twice, before the first connection completes, two panels will be opened, and one will never close

ConnectionManager.cs
- Had to add a Parameter to be able to pass back the Popup Message

MainForm.PluginsManagement
- Added a chec to see if ther eis no constructor.  The Tag has to be populated, or else a null ref exception will get thrown.  Throw a better message earlier

Added Error Logic handler if there is a Reflection Type Load Exception.
FormHelper.cs
- Added an overload for AskForConnection that accepts an Action that is called before the actual Async process is kicked off.  This allows the message to be displayed before the actual call is made.

ConnectionParameterInfo.cs
- Class to help define the parameters sent in the connection call

MainForm.cs
- Removed infoPanel field, since there may be more than one open at a time.
- Changed Parameter to be the info parameter
- Changed the infoPanel to be set wihtin the ConnectUponApproval call
MscrmTools added a commit that referenced this pull request Sep 14, 2015
Changes to prevent error with infopanel not disappearing.
@MscrmTools MscrmTools merged commit 02e9818 into MscrmTools:master Sep 14, 2015
@MscrmTools MscrmTools added this to the September 2015 release milestone Sep 14, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants