wjCore.Clipboard.copy(string) function broken since version 359

Posted by: stefan.brenner.a on 15 November 2017, 7:42 pm EST

    • Post Options:
    • Link

    Posted 15 November 2017, 7:42 pm EST

    Hi,

    I’m using the function wjCore.Clipboard.copy(string) to copy text to the clipboard. It has been working fine in drop 334 but silently fails in 359 and 380. I had a look at the source and saw that there were some changes. For example

    if (typeof (textOrCallback) == ‘string’)

    was changed to

    if (isString(textOrCallback))

    So maybe this is the cause? Please look into it and give me some feedback.

    Thanks!

  • Posted 19 November 2017, 5:31 pm EST

    HI Stefan,

    We have created a sample for testing Copy method working or not. We found that is is working fine at our end with 5.20173.380 build verison. Please refer to the attached sample for the same.

    ~Manish

    WjCore_Copy.zip

  • Posted 19 November 2017, 8:54 pm EST

    Hi Manish,

    my scenario is a little more complicated. I’m trying to overwrite the grid copying functionality to be able to copy a cell value even if row selection is active. Actually some of the code I’m using for this is from your suggestions. I attached a sample. As I said if you switch out the version to use 334 it starts working but not with 380.

    Thanks and best regards,

    StefanWjCore_Copy.zip

  • Posted 20 November 2017, 8:45 pm EST

    Hi Stefan,

    Thank you for reporting this issue and provided sample.

    We are able to replicate the issue and it seems a bug. Hence, this issue has been forwarded to the concerned team for further investigation with internal tracking id 298142.

    As a workaround, please use the following code snippet for copying selected cell content from FlexGrid:

    flex.hostElement.addEventListener("keydown",function(e){
    				if (e.ctrlKey && (e.keyCode == 67 || e.keyCode == 45)) {
    					var sel=flex.selection;
    					var copyText = flex.rows[sel.row].dataItem[flex.columns[sel.col].binding];				
    					wijmo.Clipboard.copy("" + copyText);
    					// e.preventDefault();
    					e.stopPropagation();
    					return;
    				}
    			},true);
    

    ~Manish

  • Posted 22 November 2017, 12:05 am EST

    Hi Manish,

    thanks for the workaround. Could you please inform me once this is fixed or is it possible for me to look up the state of the tracking ID?

    Thanks and best regards,

    Stefan

  • Posted 22 November 2017, 2:07 pm EST

    Hi Stefan,

    Sure, we will inform you once we get any information.

    ~Manish

  • Posted 27 November 2017, 3:08 am EST

    I’m seeing a very similar problem with pasting using wijmo.Clipboard.paste() in Wijmo v2 and v3. Previously I would get the text pasted by the user, now I get an empty string every time. I’m guessing this is related?

  • Posted 27 November 2017, 5:42 pm EST

    Hi John,

    This issue is under development. Please verify this once we update this thread with the fix. Meanwhile you can share your sample for us to verify that the reported issue is causing the behaviour in your sample.

    ~nilay

  • Posted 28 November 2017, 7:42 am EST

    http://plnkr.co/edit/X5od87zTp90yU1dXc0nj?p=preview

    With v3 libraries loaded (comment out or remove the v1 library lines in index.html):

    1: Copy the first four columns of the first two lines

    2: Move the cursor to the first column of the third line

    3: Paste

    Sample output:

    wijmo.Clipboard.paste 0

    The zero is the length of the material retrieved from the clipboard for pasting.

    With v1 libraries loaded (comment out or remove the v3 library lines in index.html):

    1: Copy the first four columns of the first two lines

    2: Move the cursor to the first column of the third line

    3: Paste

    Sample output:

    wijmo.Clipboard.paste 0 US 12/31/2013 8,104.39

    1 Germany 2/1/2014 5,920.10

    53

    There are 53 characters of data in this case on the clipboard.

  • Posted 28 November 2017, 8:47 pm EST

    Hi John,

    Thank you for the sample, I can verify that this is the same issue as reported earlier. This is under investigation by our product engineers.

    ~nilay

  • Posted 7 December 2017, 1:31 am EST

    Any ETA on a fix for this?

  • Posted 10 December 2017, 8:03 pm EST

    Hi John,

    The issue regarding paste method is still with the development team for further investigation.

    @stefan.brenner.a,

    The issue reported for Copy method has been fixed and can be verified with 5.20173.388. You may get latest build form here for testing purpose :

    http://prerelease.componentone.com/wijmo5/

    ~Manish

  • Posted 14 December 2017, 12:37 am EST

    Hi John,

    This issue has been fixed in 5.20173.391 build which can be downloaded from here for testing purpose:

    http://prerelease.componentone.com/wijmo5/

    You may also verify with the updated plunker:

    http://plnkr.co/edit/qcfIMR4BmKodBjlsjFSo?p=preview

    ~Manish

  • Posted 2 January 2018, 3:44 am EST

    I have confirmed that recent releases (I tried out build 399 and it worked well) fix this problem.

    However, because they’re public beta builds, they all display the Wijmo eval message at the bottom of the screen. How do I get an up-to-date release build which both fixes the problem and is properly licensed?

  • Posted 2 January 2018, 4:46 pm EST

    Hi John,

    We are sorry, currently, we are unable to provide any estimate time for Public licensed release. Builds are currently under QA process for next official release with licensed files.

    Once, the next release is announced, you may get it from WebSite under My-Licenses section and use in your project.

    ~Manish

  • Posted 20 September 2018, 6:31 am EST

    I am sorry but has this been released yet? Thank you very much.

  • Posted 20 September 2018, 8:49 pm EST

    Hi,

    The issue has been fixed and released. If you are facing any issue regarding this please let us know so that we may assist you accordingly.

    Regards

    Sharad

Need extra support?

Upgrade your support plan and get personal unlimited phone support with our customer engagement team

Learn More

Forum Channels