Am 07.05.2021 11:18, schrieb Alexander Wolf:
> [...]
>> Talking of features: I don't know what is 'urgent'. I can only say
>> that these operations are widely used at the planetarium:
>>
>> - deselect single constellations (instead there is the ClearAll
>> button which is ok)
>
> Well, I am the last man who changed the code for selection/deselection
> of the constellations. The code was changed to support demonstration
> in the real time mode and scripting (the stories about heavens
> fairytales), but not for direct management of selection. I think I can
> add 2 new methods (selectConstellation() and deselectConstellation())
> with the name of the constellation as parameters (probably both
> methods should be available for scripting engine also).
This would be very good. It's actually one of my aims for future
Skyculture functionality. Imagine a GUI panel which lists buttons for
all constellations of the selected skyculture, and you can select
one-by-one or customizable groups. Future topic, though, don't hold your
breath!
A scripting command can be embedded as 1-line script into a button
definition for a RemoteControl web GUI. Just make sure to run it with
the right skyculture!
If "constellation not found", do nothing but give a qDebug() to the
logfile.
>> - select/deselect single asterisms (no idea how I could solve this,
>> but showing ALL asterisms is an exotic use-case ;-)
>
> When I added support for the asterisms I did not add the selection of
> isolated asterims due simple reason: one star can be included in the
> few asterisms. I see only one way to add ability to select/deselect
> isolated asterisms: 1) do not add the feature in the GUI; 2) add 2
> methods - selectAsterism() and delesectAsterism() with names as
> parameters; 3) make both methods available through scripting engine
> and Remote Control plugin only.
For now, these functions should be scriptable and thus would be
available to a web GUI. However, as above, Skycultures 2.0 should make
that possible. Somewhere, around 2025...
The large number of asterisms with partial overlaps should allow
selection of one's favourites. (No need for parallel Winter-G and
Winter-Hexagon, for example)
>> - mark or label certain stars like "Polaris" or ['Deneb', 'Vega',
>> 'Altair']
>
> Available through scripting engine.
>
>> - smooth time transition (instead created a cosine-shaped ramp for
>> timerate and keep pushing values)
>
> Probably we may add a new method for this feature similar to
> setObserverLocation() (as in the scripting engine!) method and add the
> ability to use then in the scripting engine and Remote Control plugin.
Some extended setJD() with a smooth animation would be nice indeed.
>> - smooth location transition (pushing 30-60 requests per second is
>> not a good solution and still bucking)
>
> Available through scripting engine.
>
> If Remote Control plugin can run scripts, who was loaded through WUI
> (I hope Georg can give more info for this feature), then many "missed"
> features can be implemented through scripts.
Yes, you can assign scripts to RemoteControl buttons. There are a few
examples in the existing interface pages. (They are in need of updating
to some new functions/properties, though.)
>> and a couple of questions
>>
>> - I am using an external JS to calculate local sunset/sunrise times,
>> is it possible to query that from Stellarium?
>
> Maybe. The Remote Control plugin can call actions and we have defined
> actions to set time of those events for selected objects (see
> "actionToday_Rising" and "actionToday_Setting" actions). So, if the
> Sun selected and you called actionToday_Setting action then you will
> get the time of sunset as current time within Stellarium. Yes, this is
> 2 steps and all 9 methods were introduced to use them through
> scripting engine and shortcuts (as a real time demonstration).
:-)
>> - Can I display a label fixed to local coordinates (like date & time
>> in the south)?
>
> Yes for static text and no for dynamic text (see LabelMgr class).
>
>> - Is there a way to add scale ticks to ecliptic and grids which are
>> visible in a fisheye?
>
> Hmm... I don't see a problem with it, because this was already
> implemented a few releases ago.
Yes, did that last year or so. See the Gridlines UI in the main
application. These are not yet defined in the RemoteControl HTML
interface, but the properties are there, so that may be done rather
quickly.