Bug fix

11 Responses to “Bug fix”

---

• Denis Hamel

  April 23, 2012 at 7:47 am

  Type in one of your function:

  DeltaNuetralValidationEventArgs

  Should be

  DeltaNeutralValidationEventArgs
• jwilkins

  May 13, 2012 at 3:22 pm

  I just downloaded the latest and was updating my local code when I noticed that there’s an infinite loop in the UpdateAccountValueEventArgs class.

  Original code:

  ///
  /// The value associated with the key.
  ///
  public string Value
  {
  get { return value; }
  set { Value = value; } <– loop occurs here
  }

  I fixed this locally with the following (just thought I'd share):

  ///
  /// The value associated with the key.
  ///
  public string Value
  {
  get { return value; }
  set { this.value = value; }
  }
• rhunter

  June 25, 2012 at 8:11 pm

  Unless I add

  ///
  /// Bill
  ///
  [Description("BILL")] Bill,

  to SecurityType.cs, getting account values for an account that contains a treasury bill causes a crash.
• Karl

  June 26, 2012 at 10:13 am

  Thanks for the bug fix – just pushed it to google code.
• carga

  July 5, 2012 at 2:12 pm

  Do you improve IB-Net or do you plan to improve it further?

  At least some more samples for complicated scenarious would be useful.

  For example, how to get margin requirements for futures calendar spread? It looks like IB hides this info at all costs.

  Also it is not clear how to request ContractDetails for calendar spreads: if one have ContractID for spread, it would be much easier to send orders.

  And I’m very appreciate you for sharing your amazing library!
• CSharpy

  September 29, 2012 at 2:50 pm

  Any ideas how to wrap the events into Rx?
  Like TickPrice and TickSize event. For some reason it won’t work:

  Observable.FromEvent or
  Observable.FromEventPattern
• Fergus

  December 11, 2012 at 5:12 am

  Firstly- thank you for a wonderful library. It has saved me a lot of time and frustration over the last few years, and I’m very grateful to you for releasing it.

  I thought you might be interested that there are a few missing enumerations that I copy over manually with each release, which you may want to add to the library…

  ErrorMessage
  [Description("Cancel orders and manually remove their related legs")] CancelAndRemove = 387,
  [Description("Can't modify a filled order code")] CantModifyFilledOrder = 104,
  [Description("Market depth reset")] MarketDepthReset = 317,
  [Description("Not available for short sale")] NotAvailableForShortSale = 404,
  [Description("Cant Find Symbol err A")] CantFindSymbolA = 200,
  [Description("Cant Find Symbol err B")] CantFindSymbolB = 162

  OrderType
  [Description("PEGMID")] PeggedToMidpoint

  SecurityType
  ///
  /// Commodity
  ///
  [Description("CMDTY")] Commodity

  TimeInForce
  ///
  /// Auction
  ///
  [Description("AUC")] Auction
• INTJ

  March 13, 2013 at 11:22 pm

  I’m not a programmer, so apologies for the remedial nature of the question, but is it possible to use ibcsharp without a market data subscription? Whenever I try to use the program to make a simple equity trade using Krs.Ats.TestApp, I get the following error:

  Next Valid Id: 1
  Error: Market data farm connection is OK:usfarm
  Error: HMDS data farm connection is OK:ushmds
  Error: No security definition has been found for the request
  Error: Requested market data is not subscribed.Error&BEST/STK/Top

  I don’t need IB’s data plan, so if it’s possible to modify the code to bypass this error and just submit a simple equity trade, please let me know. Thank you.
• INTJ

  March 18, 2013 at 9:54 pm

  Apologies, I figured it out.
• pet shop in london

  April 17, 2013 at 4:29 pm

  Its like you read my mind! You seem to know so much about this, like you wrote the book in it or something.

  I think that you can do with a few pics to drive the message home a bit, but instead of that, this is excellent blog.
  An excellent read. I’ll certainly be back.
• dogs for sale

  May 4, 2013 at 1:34 pm

  This is a really good tip particularly to those new to the blogosphere.
  Brief but very accurate info… Thanks for sharing this one.
  A must read post!