Lothsahn

Show:

What's happening?

  • Followup: RE: Process Name Window Rule not working

    Steve: 1) I didn't even know about the middle click window dialog. So yes, I did overlook that feature! Very nice. 2) I understand what problem you're seeing. I would recommend the following change in functionality: a) When a dialog is loaded, no item would be selected initially. All functions to modify would be disabled, as there is no currently selected cell. Upon selecting a...

    2009-10-23 02:38:45 UTC in VirtuaWin - Virtual desktops

  • Followup: RE: Process Name Window Rule not working

    Also, the default window rule for: CabinetWClass It uses "Hide by move window" for the "Method for hiding the window". This doesn't work on my system, but "Hide using standard method" causes it to work as expected. Specifically, any folder windows that I have on my screen (from explorer, like c:\) are automatically visible on all desktops until I made this...

    2009-10-19 21:59:08 UTC in VirtuaWin - Virtual desktops

  • Followup: RE: Process Name Window Rule not working

    Awesome! That worked. I can't believe I didn't read the help for that page--it's right there now that I looked. I settled on: C:\Program Files (x86)\Pidgin\pidgin.exe Your product is working GREAT. I haven't found any significant bugs. It is really really fantastic--I used to have to deal with windows disappearing in Virtual Desktop programs. Couple minor points of feedback: 1...

    2009-10-19 21:53:40 UTC in VirtuaWin - Virtual desktops

  • Followup: RE: Process Name Window Rule not working

    My apologies--the preview looked correct with the <br> tags, but the actual post got corrupted. Please treat the <br> tags as a newline.

    2009-10-19 17:28:33 UTC in VirtuaWin - Virtual desktops

  • Process Name Window Rule not working

    I am unable to get window rules based on process name working. I am attempting to get pidgin to show on all desktops, but with no success. I tried the following process names:<br> Pidgin<br> pidgin<br> Pidgin.exe<br> pidgin.exe<br> Pidgin.exe *32<br> pidgin.exe *32<br> I see in the release notes that it should be case insensitive, so that...

    2009-10-19 17:27:52 UTC in VirtuaWin - Virtual desktops

  • Comment: SQLServer 2005: Batch updates fail if too many rows

    Attached DateOverflowTest. Reproduces the issue. I was unable to reproduce the issue again when batchSize was set. I'm not sure why. When batchSize =0: Caused by: java.sql.BatchUpdateException: I/O Error: Connection reset by peer: socket write error I've also gotten a "not enough memory to process this request". I was unable to reproduce the hanging with this testcase. This...

    2009-09-08 16:42:47 UTC in jTDS - SQL Server and Sybase JDBC driver

  • Comment: ResultSet.getInt(int) does not report integer overflow

    To clarify, this is the behavior before the fix, right? After the bug is fixed, overflow is detected in short, byte, integer, and long for both Sybase and Microsoft?.

    2009-08-10 19:15:17 UTC in jTDS - SQL Server and Sybase JDBC driver

  • Comment: SQLServer 2005: Batch updates fail if too many rows

    I can definitely still reproduce this problem. I'll try to give you a testcase to reproduce it. It's possible I'm running out of memory--this is in a util class, so maybe that's the cause (we don't have gigabytes of memory available like in the actual server application itself). batchSize didn't help for me, however. In all cases in my testing, SQLServer itself remained intact--for instance...

    2009-08-07 16:42:17 UTC in jTDS - SQL Server and Sybase JDBC driver

  • SQLServer 2005: Batch updates fail if too many rows

    I reproduced this issue against SQLServer 2005. My application attempted to do a batch execute with 402,000 rows added to the batch. In some cases, the system hangs and never completes, while in other cases, I get a socket read exception. The exception is given below. I have attempted to set the batchSize parameter, but it appears to have no effect on this problem. I was able to...

    2009-07-30 17:06:33 UTC in jTDS - SQL Server and Sybase JDBC driver

  • ResultSet.getInt(int) does not report integer overflow

    The ResultSet.getInt(int) method does not report when overflow occurs. For instance, when accessing a NUMERIC field in Sqlserver 2005 with the value 5,000,000,000, the jtds driver reports the value is approximately 700 million. This is because int is not large enough to store the value of the field. The driver should report when an integer overflow occurs. We have no way of knowing if...

    2007-12-20 19:51:30 UTC in jTDS - SQL Server and Sybase JDBC driver

About Me

  • 2002-04-05 (8 years ago)
  • 506414
  • lothsahn (My Site)
  • Lothsahn

Send me a message