Beiträge von Rylee

    Hi,

    I am writing a tool to draw on a krpano viewer. Part of this is dynamically creating polygonal hotspots, much like the example given in the "addhotspot" documentation.

    The problem is that I cannot delete any of these points — how do I delete a single point? Is this even possible?

    EDIT: things I have tried (that do not work):

    Code
    removehotspot(hotspot[polyspot].point[3])
    delete(hotspot[polyspot].point[3])
    delete(hotspot[polyspot].point['n3']

    Hello,

    Upon setting [1] as the URL of one of my layers, I get a "Security Error". Is there any way to use a data URI as a layer URL?

    [1]:

    Code
    data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAJYAAAAeCAMAAAD5PBdlAAAABGdBTUEAALGPC/xhBQAAAAFzUkdCAK7OHOkAAAAgY0hSTQAAeiYAAICEAAD6AAAAgOgAAHUwAADqYAAAOpgAABdwnLpRPAAAAXFQTFRF////+vr6cHBweHh4Nzc3r6+vAAAAvr6+CQkJpKSkCwsLBwcHHh4e/Pz8oKCgPz8/DQ0NAwMDISEhbGxs4+Pj4ODgbm5uBQUF6+vrw8PDRkZGWFhYycnJKysr7OzsPT09ampqzc3NwMDANjY2ERERysrKBAQEFRUV+/v7wsLCODg4ZGRk5ubmIyMjgICAnJyc8/PzIiIijY2NmZmZzs7OREREu7u7+fn5LS0tXl5ePj4+/f39MzMzBgYGhYWFy8vLAgICLy8v3t7e8fHxd3d3e3t70dHR5OTk9vb2ICAgGhoa8PDwubm50tLSZWVl2NjYb29v+Pj4jIyMDg4O6enp6urq/v7+enp69fX1Li4uLCwsU1NTSEhIOjo6xsbGhoaGcnJytra2z8/P29vbnp6eYGBg9PT0JCQkdnZ2yMjIlZWVKCgo39/fXV1dExMTvLy8ZmZmzMzMVlZWAQEBEBAQSkpKtLS0xcXF09PTX19fkpKSSJ5XPwAAAAFiS0dEAIgFHUgAAAAJcEhZcwAAAEgAAABIAEbJaz4AAAGCSURBVFjD7ZRXU8JAFEaDyicSLFGKIGKXKLaoiCAo2DsqgiLYFXvv/np34/iQ+JKHzOI4OQ97N/d+M3sms7McZ2DwpzCV6BnTjdIyPWN6YYam8zTG9KLcouk8jTG9qLAC4Hkb3VdWVdcItXV2snU4Sd/lrHd7IDR4lTE2NP78Bl9Tc4u9tQ3tHfTL3Qm/SHz4LlWMsZbYHaClx4VekW76gH5uQBpU2zPWGsKwXIPACK2hUfh94chYkbWiiPGUTkEYlxsTcSRqJtUxxlpTQEg1mQZmftkz1poF5lST+QUsLhVZywssqyYrFmC1yFpJYO2nNbtO11BiIwKUF02rTZawILX53UkHM7RsRcUkD2lbEWNGFjtyzQF5+dIv7Zpp2YuRB2MfOFDGWJGHK835DrkjAYiaHccn0iltF87OyWrKIn6hiLHiErgKRK857oR4UcIm0s3c3Bbo9A6Q0ooYI0z3VmtOPu7h0f/0/PJKL9abB6k+8sC/fxBP26ciZmBgYPDf+QJWsTMqGUnl9AAAAAx0RVh0Y2FwdGlvbgB0ZXh0f3TDqAAAACV0RVh0ZGF0ZTpjcmVhdGUAMjAxNC0xMS0xMFQxODozMjo0NCswMDowMDnlElwAAAAldEVYdGRhdGU6bW9kaWZ5ADIwMTQtMTEtMTBUMTg6MzI6NDQrMDA6MDBIuKrgAAAAAElFTkSuQmCC

    A developer menu for krpano that would be able to display actions per frame, enable tracing each action as it is executed, and other useful functions for developing an advanced krpano application, would be obscenely useful to me as a developer. It's extremely difficult to debug applications at the current time with the set of tools that we have (Javascript API and `trace()`).

    I have a function that iterates over the indices between two elements to automatically align them to a certain standard. This works deterministically in the HTML5 viewer -- that is to say, I always get the result I'm looking for in the HTML5 viewer. However, in the Flash viewer, the indices seem to be in a random order, so that two child elements will not have consecutive indices.

    Example code follows.

    Code
    <layer name="main_sidebar" keep="true"
      type="container"
    > <!-- and other various positioning things... -->
    <layer name="sub_tab_one" keep="true" style="my_tab_style" /> <!-- and other styling and positioning things -->
    <layer name="sub_tab_two" keep="true" style="my_tab_style" />
    <layer name="sub_tab_three" keep="true" style="my_tab_style" />
    <!-- and so on... -->
    </layer>

    One would expect `layer[sub_tab_one].index`, `layer[sub_tab_two].index`, and `layer[sub_tab_three].index` to be consecutive, and they are in the HTML5 viewer. However, in the Flash viewer, the order of indices is unpredictable. Is there any way around this?

    Alternatively, is there any easy way to iterate over the child elements of a layer?

    Hey,

    I work at a company that uses Alpine Linux somewhat extensively and would like to expand its use. The only downside is that krpanotools does not support musl (or any alternate libcs, for that matter.)


    Example run of `krpanotools` on a distribution using `musl`.

    I would like to formally request a build of krpanotools that is statically linked instead of dynamically linked. This would result in greatly increased compatibility and zero dependency on the system libc being in or out of date.