[Kst] pixel type marker missing in Kst 2.x (as opposed to 1.6/1.7) ?

[Daniel Mader]

Hi Barth,

Cool :) Here's the bug number for your reference:
https://bugs.kde.org/show_bug.cgi?id=337574

We'll be able to compile from source once this feature is added, thanks a lot in advance, both for KST and your continued efforts!

Best regards from Munich,
Daniel

-----Ursprüngliche Nachricht-----

Ohh... OK.  Thanks.  I can very easily fix this.

Can you report a wishlist bug so I don't forget?

cbn

On July 17, 2014 3:20:10 PM Daniel Mader wrote:

> Hello Barth, it seems I've misspelled your address, here's a new try...
> 
> -----Ursprüngliche Nachricht-----
> Good morning Barth,
> 
> thanks for getting back to me!
> 
> As for the feature, in 2.x there are only larger points available now, i.e.
> complex markers such as squares, circles, and characters, but no 'pixel'
> marker. This was well available in the 1.x series.
> 
> With Python's matplotlib, you'd get this marker style like this.
> 
> import matplotlib.pyplot as plt
> fig = plt.figure(figsize=(20,20))
> ax1 = fig.add_subplot(111)
> ax1.grid()
> ax1.plot(range(1024), range(1024), ',') # <=== mind the comma!
> fig.suptitle('fig title')
> ax1.set_title('ax title')
> ax1.set_xlabel('xlabel')
> ax1.set_ylabel('ylabel')
> ax1.set_xlim(left=None, right=None)
> ax1.set_ylim(bottom=None, top=None)
> ax1.legend(loc='best', numpoints=1)
> fig.show()
> fig.savefig('test.pdf')
> 
> It is incredibly usefull if you need maximum resolution in order to 
> prevent dots from overlapping. In our case, if you test a CCD for dirt 
> or broken pixels and display this on a screen, it is the only way that makes sense...
> 
> Any suggestions would be deeply appreciated!