| Bugs item #2948926, was opened at 2010-02-10 03:35
Message generated for change (Comment added) made by mantaraya36
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=564599&aid=2948926&group_id=81968
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: qutesound
Group: None
Status: Closed
Resolution: Works For Me
Priority: 5
Private: No
Submitted By: Jim Michaels (jmichae3)
Assigned to: Andres Cabrera (mantaraya36)
Summary: cut and paste do not use windows clipboard
Initial Comment:
cut and paste operations do not use the windows clipboard.
impossible to work with outside text editors like Crimson/Emerald Editor or Notepad just to copy and Paste and get any decent work done.
GetClipboardOwner()
GetClipboardFormatName()
GetClipboardData()
GetClipboardDataAlloc()
SetClipboardData()
these are win32 functions which govern the clipboard which you would probably use. look for them on http://msdn.microsoft.com and look for the Windows Function.
I don't know what the mac equivelant is. If qutesound is written in python, I suggest you use a python module that can handle using the windows clipboard.
another issue I ran into is that the newline sequences used by the program are not windows-compatible. windows uses a cr+lf. when working with the clipboard, some translation should be done if you wish to keep your existing format but work with Windows clipboards.
Mac I think uses purely lf - or was it cr only?. someone correct me on the current mac standard.
I suggest using ANSI rather than UNICODE, though that may be an issue for some countries.
----------------------------------------------------------------------
Comment By: Andres Cabrera (mantaraya36)
Date: 2010-02-25 13:08
Message:
QuteCsound has it's own bug tracker here:
https://sourceforge.net/tracker/?group_id=227265
I have added a feature enhancement to make windows use the standard
windows line break.
----------------------------------------------------------------------
Comment By: Jim Michaels (jmichae3)
Date: 2010-02-25 01:47
Message:
I was talking about qutesound. sorry. not lr. cr (carriage return). lf is
line feed. if the examples are simply text files, then they would also
need to have their line endings fixed for windows. and the editor would
also need to edit using cr+lf. (i just typed lr again - it's this split
ergo keyboard throwing me for a loop causing me to typo - it's my fault.
sorry)
the functions I gave were win32 functions available in a windows system
DLL: user32.dll
you can find documentation on them in http://msdn.microsoft.com
----------------------------------------------------------------------
Comment By: Andres Cabrera (mantaraya36)
Date: 2010-02-24 03:53
Message:
Hi,
The issue with the clipboard on Windows is known and its cause is the FLTK
library, which for some yet unknown reason grabs the clipboard and won't
release it after the first csound run. The current workaround is
unfortunately to disable the FLTK opcodes.
I am not using those functions, since I use the clipboard provided by Qt,
which wraps platform specific clipboard functions. I haven't checked, but I
would think the usage of the clipboard by Qt is kosher, so using those
functions directly in QuteCsound will probably not work anyway...
The simplest method to do this is sopying the opcodes directory from the
Csound directory to a new one and removing widgets.dll and virtual.dll from
that directory. Then it is necessary to point OPCODEDIR in the Environment
tab in the QuteCsound configuration. If you want to use the FLTK opcodes
(but lose the clipboard...) you can disable usage of OPCODE dir by
unchecking it.
Thanks for your suggestions about lf. The problem is that since QuteCsound
is a cross-platform program it must support all platforms wiht the minimum
denominator. Unfortunately the three main platforms all use different
systems foe new line. Windows uses lf+lr, mac and linux use lf mostly (but
older mac OSs < 10 used lr only), so the choice was made to support lf to
enable easy interchange of files. I was not awarw that this would break the
windows clipboard.
I will see if something can be done so that the clipboard uses lf+lr.
ANSI will definitely break things for many users of non-standard
characters. UNICODE is standard on OS X and Linux (and I think should be
well -better...- supported on Windows...).
----------------------------------------------------------------------
Comment By: John ffitch (jpff)
Date: 2010-02-24 01:12
Message:
Is this csound? I do not recognise any of those names/functions. Is this
qutesound?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=564599&aid=2948926&group_id=81968
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net |