ScriptUO

Scripting Resources & Utilities => ScriptUO Application => Feedback => Topic started by: TrailMyx on November 03, 2008, 02:50:43 PM

Title: Anyone have problems with cut/copy to the clipboard?
Post by: TrailMyx on November 03, 2008, 02:50:43 PM

I'm curious because I have one computer (Win XP Home) that will crash when I try to cut/copy to the clipboard.  It's odd.

Title: Re: Anyone have problems with cut/copy to the clipboard?
Post by: Cstalker on November 03, 2008, 06:57:34 PM

I had a crash today, but i was runing 3 clients, 1 doing bods, one exporting bods, another running around testing a script, and workign on a 4 script. but i think that was more ie and it only happened once.

Title: Re: Anyone have problems with cut/copy to the clipboard?
Post by: Endless Night on November 04, 2008, 06:12:59 AM

I dont seem to be having any issues.

Title: Re: Anyone have problems with cut/copy to the clipboard?
Post by: Xclio on November 04, 2008, 06:48:27 AM

I haven't seen anything yet.

Title: Re: Anyone have problems with cut/copy to the clipboard?
Post by: Superslayer on February 17, 2009, 06:29:47 PM

I'm beginning to experience odd things with it.  Using v.224 I've noticed that my copy\paste doesn't always 'apply'.  I copy/paste back and forth with SUO and EUO for syntax and indent.  Randomly, either one doesn't delete/paste from one to the other unless I re-select all and rc  to delete.  Sometimes even that doesn't work so I pull out the old delete button itself or go to the actual title bar "Edit" option.  Again, randomly and between both engines.  No biggie imo, but annoying after a few hours or working on a script.

Title: Re: Anyone have problems with cut/copy to the clipboard?
Post by: TrailMyx on February 17, 2009, 07:07:20 PM

Ya, it's strange because it comes and goes.  With the debugger, the application will actually crash within the windows paste facility (not my code or the ICSharpCode.Editor control) You're noticing the paste not working because I'm simply ignoring the actual windows exception that's occurring (I kinda thought that would be better than a terminal exception... heh)  I'm not sure why that is; more .NET strangeness.