Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Pleiades

Pages: 1 [2] 3 4 ... 6
This forum board is for image processing challenges and exercises made exclusively with PixInsight. Please do not use it to post or comment results produced with other image processing or editing applications, even if their contribution is minimal. If in doubt, or if you think that a particular image or result can be of special interest to the forum community, please ask the forum moderators before posting it.

This forum board is for workshops, conferences and talks exclusively about image processing or development with PixInsight. Please do not use it to promote or announce events or talks not related to PixInsight. If in doubt, or if you think that a particular event can be of special interest to the forum community, please ask the forum moderators before posting your announcement.

Gallery / Gallery Rules - Please read before posting
« on: 2014 March 08 11:02:13 »
This forum board is for images processed exclusively with PixInsight. Please read the forum's image posting rules before posting your image.

Gallery / MOVED: Image calibration - Pixinsight and CCD-Stack
« on: 2013 November 14 00:56:47 »

Gallery / MOVED: Astrophoto Prints
« on: 2013 November 14 00:54:21 »

Hi All,

Today we have had two cancellations for the Munich workshop, so there are two seats available now. If you are interested in attending this workshop, please contact Vicent Peris ASAP.

Thank you.

Bug Reports / MOVED: TGVDenoise update did not take
« on: 2013 May 20 01:50:53 »

PixInsight Forum is a spam-free service. We are constantly improving our software and security resources to guarantee that no spammer (neither human nor machine/automatic) will be able to enter here.

One of those security measures is that all forum membership requests are revised and approved or rejected manually by our maintenance staff. No forum membership is approved until we are able to identify the requesting  person as either one of our users (both trial and commercial licenses are equally valid) or as an individual that has not been involved with spamming activities.

To facilitate our task, and to accelerate our approval of your forum membership, please bear in mind the following when you send us a forum registration request:

  • If you register with the same email address you have associated with your license(s) (trial and/or commercial), then in general we'll approve your request immediately.
  • If you want to register with a different email address for some reason—for example, because you are not a PixInsight user—, then please use that email address to write us (you can use our online contact form) specifying your full name, your requested forum user name, and that you are an individual involved with astronomy, astrophotography, science, technology, arts, etc., so we can verify that you are not a spammer. Some links to web pages or documents that identify you can also be of great help.

Thank you for your attention, and see you on PixInsight Forum!

The PixInsight Team at Pleiades Astrophoto S.L.

Hi all,

This is to remind you that the July 2011astrophotography contest is now open on PixInsight Forum. The deadline for submitting images is July 20th.

If you wish to participate, please post your image to the corresponding forum thread:

The contest rules are available here:

Thank you and good luck!

but then we won't have the nice modal dialog reporting all the progress, FWHM monitor etc...?

Correct. That's why your ImagingSession container makes a lot of sense.

Would the thread be able to assign that?

Yes, a thread can modify an image, even if it is an image living in the core application (inside a view). As long as you guarantee that two or more threads won't modify the same pixel concurrently (using mutexes if required), everything will be fine.

But I thought that the thread couldn't call anything that updates the UI?

A thread cannot perform any GUI operation. However, writing and copying pixels has nothing to do with the GUI. What a thread cannot do, for example, is call ImageWindow::Show() for example. As long as the operations that you carry out don't imply (directly or indirectly) a GUI update —which means drawing on the screen, essentially—, there should be no problems.

Pages: 1 [2] 3 4 ... 6