Lieber Besucher, herzlich willkommen bei: krpano.com Forum. Falls dies Ihr erster Besuch auf dieser Seite ist, lesen Sie sich bitte die Hilfe durch. Dort wird Ihnen die Bedienung dieser Seite näher erläutert. Darüber hinaus sollten Sie sich registrieren, um alle Funktionen dieser Seite nutzen zu können. Benutzen Sie das Registrierungsformular, um sich zu registrieren oder informieren Sie sich ausführlich über den Registrierungsvorgang. Falls Sie sich bereits zu einem früheren Zeitpunkt registriert haben, können Sie sich hier anmelden.
The functionality of the added hotspot is based on the 'skin_hotspotstyle' style and without vtourskin.xml this can be guaranteed. Therefore the editor simply checks if there is the text 'vtourskin.xml' anywhere in the xml before enabling the editing functionally.Found out, that if you use an own tour.xml, not that one that's generated by the VTOUR droplet, I can`t add/edit hotspots.
With the old flashPlayer Version it was/is working...
My panos are also seperated in scenes like in your tour.xml, but I don`t use the "vtourskin.xml" and the "skin_settings"...
Hmm, I see, this is unfortunately a side effect of the 'Avoid a screen blinking on iOS when touching a textfield in some cases' fix...Ummm...this update totally killed all the (html) input fields in our plugins. Works well with 1.19 pr10, does not in pr13. Any ideas?
|
|
Quellcode |
1 |
inputelement.addEventListener("mousedown", function(e){ e.stopPropagation(); }, true);
|
Benutzerinformationen überspringen
Wohnort: Netherlands
Beruf: Krpano custom coding / Virtual Tours / Photography / Musician / Recording engineer
: https://pame.virtualtuur.comDieser Beitrag wurde bereits 1 mal editiert, zuletzt von »Reggie« (29. September 2017, 20:40)
|
|
Quellcode |
1 |
html= "[img src='path_to_png' style='width:24px; height:16px; margin:0px 0px -4px -2px; ' /] Language_text" |
Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »pur« (6. Oktober 2017, 00:26) aus folgendem Grund: The syntax [sq] for textfield html and caption has been used.
Perfect! Copy vtourskin.xml in my tour.xml and the editor works...The functionality of the added hotspot is based on the 'skin_hotspotstyle' style and without vtourskin.xml this can be guaranteed. Therefore the editor simply checks if there is the text 'vtourskin.xml' anywhere in the xml before enabling the editing functionally.Found out, that if you use an own tour.xml, not that one that's generated by the VTOUR droplet, I can`t add/edit hotspots.
With the old flashPlayer Version it was/is working...
My panos are also seperated in scenes like in your tour.xml, but I don`t use the "vtourskin.xml" and the "skin_settings"...
|
|
Quellcode |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 |
/*
krpano - super simple html5 text input plugin
*/
var krpanoplugin = function()
{
var local = this;
var krpano = null;
var plugin = null;
var inputelement = null;
local.registerplugin = function(krpanointerface, pluginpath, pluginobject)
{
krpano = krpanointerface;
plugin = pluginobject;
inputelement = document.createElement("input");
inputelement.type = "text"
inputelement.style.width = "100%";
inputelement.style.height = "100%";
plugin.registerattribute("text", "", text_set, text_get);
plugin.registerattribute("onchanged", null);
plugin.registerattribute("onkeydown", null);
inputelement.addEventListener("change", text_changed, true);
inputelement.addEventListener("keydown", text_keyDown, true);
inputelement.addEventListener('touchstart',text_click, true); // Android & iPhone
plugin.sprite.appendChild(inputelement);
}
local.unloadplugin = function()
{
plugin = null;
krpano = null;
}
function text_set(newtext)
{
inputelement.value = newtext;
}
function text_get()
{
return inputelement.value;
}
function text_changed()
{
krpano.call(plugin.onchanged, plugin);
}
function text_keyDown(event)
{
krpano.set('keycode',event.keyCode);
krpano.call(plugin.onkeydown, plugin);
}
function text_click(event)
{
event.target.focus();
}
};
|
Dieser Beitrag wurde bereits 2 mal editiert, zuletzt von »MrTie« (5. Oktober 2017, 10:38)
Maybe this help...hI Klaus, my input plugin dont works in 1.19.13 ( and work in 12)
Dear Klaus,Hmm, I see, this is unfortunately a side effect of the 'Avoid a screen blinking on iOS when touching a textfield in some cases' fix...Ummm...this update totally killed all the (html) input fields in our plugins. Works well with 1.19 pr10, does not in pr13. Any ideas?
I will look for fixing this while keeping the iOS problem fixed too...
For a manual solution it would be possible to edit the textinput.js by adding this line in the registerplugin function:
![]()
Quellcode
1inputelement.addEventListener("mousedown", function(e){ e.stopPropagation(); }, true);
Best regards,
Klaus
|
|
Quellcode |
1 |
$("input").off("touchstart").on("touchstart", function(e) {$(e.currentTarget).focus()});
|
Hi,The new combobox is awesome, but in new build, despite using "tooltips_mapspots="true" in skin settings, the mapspot tooltips are not showing on mouseover for Google Maps.
Also worth mentioning is that I get an error message when opening the new Tour Editor that says "plugins/scrollarea.js failed to load (0)" even though the scrollarea.js is in the plugins folder. Once hotspots are added to the panos using the editor, they show a tooltip on mouseover, but mapspots do not.
I really need tooltips for the mapspots in this project and would be gratefui to learn of a solution or workaround for this.
Regards, Reggie
|
|
Quellcode |
1 2 3 |
<action name="skin_addmapspots"> for(set(i,0), i LT scene.count, inc(i), if(scene[get(i)].lat, txtadd(spotname, 'spot', get(i)); txtadd(spotclickevent, 'skin_hidetooltips(); activatespot(',get(spotname),'); skin_loadscene(', get(scene[get(i)].name), ',get(skin_settings.loadscene_blend)); skin_updatescroll(); delayedcall(0.5,skin_showmap(false));'); copy(scene[get(i)].mapspotname, spotname); addspot(get(spotname), get(scene[get(i)].lat), get(scene[get(i)].lng), get(scene[get(i)].heading), false, get(spotclickevent), null); if(skin_settings.tooltips_mapspots, set(layer[skin_map].spot[get(spotname)].tooltip, get(scene[get(i)].title) ); txtadd(layer[skin_map].spot[get(spotname)].onover, 'set(hovering,true);', 'copy(layer[skin_tooltip].html, tooltip); set(layer[skin_tooltip].visible, true); tween(layer[skin_tooltip].alpha, 1.0, 0.1); asyncloop(hovering, copy(layer[skin_tooltip].x,mouse.stagex); copy(layer[skin_tooltip].y,mouse.stagey); );' ); txtadd(layer[skin_map].spot[get(spotname)].onout, 'set(hovering,false);', 'tween(layer[skin_tooltip].alpha, 0.0, 0.1, default, set(layer[skin_tooltip].visible,false), copy(layer[skin_tooltip].x,mouse.stagex); copy(layer[skin_tooltip].y,mouse.stagey); );' ); ); ); );
if(xml.scene != null, activatespot( get(scene[get(xml.scene)].mapspotname) ); , activatespot(spot0); );
<!-- zoom and pan the map to see all spots at the same time --> zoomToSpotsExtent(); </action>
|
why are you using calc for this?
trace(style[mystyle].bgborder); is enough