David,
sorry for having yet another question.
To logically group two plots, I created a Groupbox $box and then in 4box
$plot1 (name=name1) and $plot2 (name=>name2).
Now I try to access from $plot2 datasets in $box->{name1}. But it does
not exist!
I know that Groupbox is probably the wrong tool, but what are better ones?
On 07/29/2013 05:45 PM, David Mertens wrote:
> In short, no, alpha-transparency is not supported.
That's unfortunate! Any chance this will change? Is it difficult to
implement?
Ingo
>
> I brought up an idea on the Prima mailing list for how it might be
> supported. Dmitry proposed a different idea, and it stalled at that
> point. In a fit of open-source frenzy, I read about alpha image
> compositing, but I never actually sat down to study the mechanisms
> available to actually Get It Done. For example, fonts are drawn with
> anti-aliasing, so there is an approach already in place for drawing
> alpha-transparency. But it might be font specific. And then I
> distracted myself with something else. :-)
>
> David
>
>
> On Mon, Jul 29, 2013 at 9:08 AM, Ingo Schmid <[email protected]
> <mailto:[email protected]>> wrote:
>
>
>
> Hi David,
>
> good to hear you found a job you liked. I like mine and therefore
> I only use PDL ;).
>
> I need and am working on something to browse through ND data,
> besides performing operations on them, So a selection of 2 dims to
> view, while allowing to scroll through the others. Then adding
> smoothing, filtering, arithmetics, overlays ...
>
> I do have a question to you, though. Is it possible to overlay two
> images and make at least one semi-transparent? I have not
> investigated thoroughly but from browsing the docs was not clear
> to me.
>
> Ingo
>
>
> On 07/29/2013 02:45 PM, David Mertens wrote:
>> Ingo -
>>
>> I'm so sorry I never replied to your question. I'm glad you got
>> it sorted out. Craig, thanks for pointing Ingo in the right
>> direction. The grid plottypes are incredibly slow compared with a
>> straight raster rendering of a piddle, but is necessary for
>> nontrivial x/y scaling types (i.e. logarithmic). In the back of
>> my head, I plan to write a piddle viewer widget that not only
>> turns a 2D piddle into an image, but a 3D piddle into a movie.
>>
>> I've spent almost not time hacking on Perl stuff lately, but
>> that's because I really like my new job, so I'm putting all of my
>> energy into it at the moment. It's nice to have a job again in
>> which I *want* to put all of my energy. My plotting library
>> gained a fair amount of new features while I was in my last job,
>> and that does not speak well to the job. :-)
>>
>> Anyway, glad you figured it out!
>>
>> David
>>
>>
>> On Wed, Jul 24, 2013 at 9:20 AM, Ingo Schmid <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>> Hi,
>>
>> I'm so sorry, my last message was hasty, please forget it.
>>
>> It works!
>>
>> For some reason the button info is twice in the argument
>> list, so it
>> received always the same x value and the y value was x.
>> Thank you for your patience.
>>
>> Ingo
>>
>> On 07/24/2013 02:54 PM, Craig DeForest wrote:
>> > Hmmm...
>> >
>> > To be honest, I never got beyond using Prima::Simple before
>> I ran out of development hours last winter. This is probably
>> a question best posed to David directly.
>> >
>> >
>> > On Jul 24, 2013, at 6:47 AM, Ingo Schmid <[email protected]
>> <mailto:[email protected]>> wrote:
>> >
>> >>
>> >> Hi,
>> >>
>> >> I was wrong, it only works when using Prima::Simple. When
>> changing the
>> >> sample code to use Prima::Application and embed the plot
>> in a window, it
>> >> stops working.
>> >>
>> >> Ingo
>> >>
>> >> On 07/23/2013 06:57 PM, Ingo Schmid wrote:
>> >>> Craig,
>> >>> The example is really what I was looking for,
>> unfortunately it behaves
>> >>> very strange for Grid data types. The onMouseMove event
>> is captured only
>> >>> extremely sporadically after leaving and entering the
>> area, I think, but
>> >>> not always even then.
>> >>> Thanks for pointing me there, I overlooked it.
>> >>> Ingo
>> >>>
>> >>>
>> >>>
>> >>> On 07/22/2013 05:00 PM, Craig DeForest wrote:
>> >>>> Argh, wit d'escalier is strong today. I should have
>> pointed out:
>> >>>> (a) the lines you want are 485ff in that code
>> >>>> (b) the methods aren't mine, they're David's -- that's
>> just an example of how to use 'em.
>> >>>>
>> >>>>
>> >>>> On Jul 22, 2013, at 8:58 AM, Craig DeForest
>> <[email protected]
>> <mailto:[email protected]>> wrote:
>> >>>>
>> >>>>> Hi, Ingo,
>> >>>>>
>> >>>>> You might like to have a look at the justification code in
>> >>>>> PDL::Graphics::Simple::Prima.pm. The plot obect has
>> methods ->reals_to_pixels()
>> >>>>> and ->pixels_to_reals(), to convert between pixel
>> coordinates and scientific
>> >>>>> coordinates. That might fit the bill for you.
>> >>>>>
>> >>>>> Cheers,
>> >>>>> Craig
>> >>>>>
>> >>>>>
>> >>>>> On Jul 22, 2013, at 7:26 AM, Ingo Schmid
>> <[email protected] <mailto:[email protected]>> wrote:
>> >>>>>
>> >>>>>> On 07/22/2013 01:05 PM, Dmitry Karasik wrote:
>> >>>>>>>> A nice job for a Prima application, I thought.
>> >>>>>>>>
>> >>>>>>>> a) Is there a simple way to get the pixel position
>> in the data piddle
>> >>>>>>>> from the mouse position?
>> >>>>>>>>
>> >>>>>>>> b) how can I lock images (placed next to each other)
>> together so that
>> >>>>>>>> when I moveor zoom one, the other one gets
>> moved/zoomed as well?
>> >>>>>>> Hi Ingo,
>> >>>>>>>
>> >>>>>>> I can't answer these without digging pgp's source
>> code, perhaps David
>> >>>>>>> could answer?
>> >>>>>> Hi,
>> >>>>>> to explain what I mean, when you use gnuplot, the wxt
>> terminal prints
>> >>>>>> dataset's x/y pairs when moving over the plot. Can I
>> get those from
>> >>>>>> Pirma images?
>> >>>>>>
>> >>>>>> I just looked at an old perl-tk program, there I had
>> calls to
>> >>>>>> $Tk::event->x which at least gave mi the position
>> within the widget. Can
>> >>>>>> I get those, at least?
>> >>>>>>
>> >>>>>> Ingo
>> >>>>>>
>> >>>>>> _______________________________________________
>> >>>>>> Perldl mailing list
>> >>>>>> [email protected] <mailto:[email protected]>
>> >>>>>> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
>> >>>>>>
>> >>> _______________________________________________
>> >>> Perldl mailing list
>> >>> [email protected] <mailto:[email protected]>
>> >>> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
>> >>>
>> >>
>> >> _______________________________________________
>> >> Perldl mailing list
>> >> [email protected] <mailto:[email protected]>
>> >> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
>> >>
>> >
>>
>>
>> _______________________________________________
>> Perldl mailing list
>> [email protected] <mailto:[email protected]>
>> http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
>>
>>
>>
>>
>> --
>> "Debugging is twice as hard as writing the code in the first place.
>> Therefore, if you write the code as cleverly as possible, you are,
>> by definition, not smart enough to debug it." -- Brian Kernighan
>
>
>
>
> --
> "Debugging is twice as hard as writing the code in the first place.
> Therefore, if you write the code as cleverly as possible, you are,
> by definition, not smart enough to debug it." -- Brian Kernighan
_______________________________________________
Perldl mailing list
[email protected]
http://mailman.jach.hawaii.edu/mailman/listinfo/perldl
