Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 1299 - Drawing back image not working
Summary: Drawing back image not working
Status: RESOLVED FIXED
Alias: None
Product: .NET TeeChart
Classification: Unclassified
Component: Xamarin.Forms (show other bugs)
Version: TeeChart.NET 2014 4.1.2014.12154
Hardware: PC Windows
: High normal
Target Milestone: ---
Assignee: Steema Issue Manager
URL: http://stackoverflow.com/questions/32...
Keywords:
: 1295 (view as bug list)
Depends on:
Blocks:
 
Reported: 2015-09-10 06:39 EDT by narcís calvet
Modified: 2016-06-15 06:53 EDT (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description narcís calvet 2015-09-10 06:39:18 EDT
It doesn't work either assigning an image to the back wall or panel:

      var backImage = new Image();
      backImage.Source = ImageSource.FromUri(new Uri("http://www.steema.com/uploads/news/xamarinforms_280x210.png"));

      tChart1.Walls.Back.Gradient.Visible = false;
      tChart1.Walls.Back.Image = backImage;

      tChart1.Panel.Gradient.Visible = false;
      tChart1.Panel.Image = backImage;

nor drawing it directly on the canvas:

    void tChart1_BeforeDrawSeries(object sender, Graphics3D g)
    {
      Rectangle chartRect = tChart1.Chart.ChartRect;
      var backImage = new Image();
      backImage.Source = ImageSource.FromUri(new Uri("http://www.steema.com/uploads/news/xamarinforms_280x210.png"));

      g.Draw(chartRect, chartRect, backImage, false);
    }
Comment 1 narcís calvet 2015-09-10 06:50:13 EDT
Happens both in iOS and Android.
Comment 2 Emmanuel 2015-11-19 10:23:57 EST
Got the same problem
Comment 3 narcís calvet 2015-11-25 06:06:47 EST
*** Bug 1295 has been marked as a duplicate of this bug. ***