Parenthesis characters stripped?

• 
  Hi there,
  
  
  Interesting. That's definitely a bug. I'm aware that there are issues with certain characters within snippets in the current implementation, so I imagine this is a manifestation of that problem. I apologise for the aggravation it's causing you. Which editor are you using, and have you found this to be editor specific or do you get it with all editors? At any rate, we'll make sure it's fixed in version 3.
  
  
  Thanks,
  Bart

  Bart Read June 02, 2006 05:21

  - 0 +
• 
  SQL Server 2000 Query Analyzer

  larthallor June 02, 2006 09:18

  - 0 +
• 
  That is, I've only tried it in QA.

  larthallor June 02, 2006 12:29

  - 0 +
• 
  It's happening within the SQLPrompt snippit tester as well.
  This is a big problem for me since I have (HAD) ... since lost them all yesterday after installing SQLPrompt.... may snippits that use parens
  
  Things such as:
  IF NOT EXISTS (select * from dbo.sysobjects where id = object_id(N'[dbo].[TABLENAME]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
  
  I hope I don't have to pay for 3.0 since I've lost functionality by moving from PromptSQL to SQLPrompt... This DID work in PromptSQL !!!

  haljc June 02, 2006 13:04

  - 0 +
• 
  Hi,
  
  We use the System.Windows.Forms.SendKeys class for inserting snippets into editors. Because parethesis have a special meaning in SendKeys you have to escape them using curly braces, eg. '{(}'.
  
  For a full description of the SendKeys syntax see here
  
  http://msdn2.microsoft.com/en-us/library/system.windows.forms.sendkeys.aspx
  
  Hope that helps,
  
  Tilman

  Tilman June 06, 2006 06:25

  - 0 +
• 
  So, the next revision is going to escape these characters prior to sending them to SendKeys.Send(), right?

  larthallor June 06, 2006 09:44

  - 0 +
• 
  Hi,
  
  Not sure about this, as parentheses have a useful purpose, i.e. they are used to specify the scope of the Ctrl, Alt, and Shift key. Escaping parentheses automatically would mean that this functionality was lost.
  
  Regards,
  
  Tilman

  Tilman June 06, 2006 10:53

  - 0 +
• 
  since they are using SenKeys for the data just replace the ( with +9 and the ) with +0 in the code.
  
  Example:
  IF NOT EXISTS +9select * from dbo.sysobjects where id = object_id+9N'[dbo].[TABLENAME]'+0 and OBJECTPROPERTY+9id, N'IsUserTable'+0 = 1+0
  
  Example:
  Insert Into MyTable
  +9
  Myfield1
  +0
  Values
  +9
  'Test'
  +0

  tieman123 June 14, 2006 11:06

  - 0 +
• 
  How about adding a check box to that indicates whether the entered text should be escaped so that it comes out as-typed or is raw send keys text?

  larthallor June 14, 2006 13:07

  - 0 +
• 
  Hi,
  
  that's a good idea. I will add it to the list of suggestions.
  
  Thanks,
  
  Tilman

  Tilman June 15, 2006 03:52

  - 0 +

Add comment

Please sign in to leave a comment.