I've created a custom module based on people template.
i've customised the editView (which is synced with the detailView) and I have assigned a tabindex value for every field.
But when I use that editView almost every field has tabindex=-1 so I only can't get to them using my mouse, which is very slow.
I was changing include/EditView/EditView.tpl but it looks the changes there has no effect on the generated code.
I changed all tabindex=$tabindex for a tabindex="-3", "-4", "5" in every tabindex assignment, but I couldn't see it in my html page, I also tried making a QRR previously.
So my question is where can I fix that -1 issue or, at least, where is really being generated my editView.
Thanks in advance!!!
Well! I found a workaround... I guessed that the problem was the autogenerated fields, they had no "space" among another fields's tabindex values...
So, instead of giving the fields tabindex values of 1, 2, 3, 4... I gave them as 10, 20, 30, 40...
And, against all odds, it works!
Perhaps it's useful for somebody....
Well, I finally found where this fields, and tabindex values of course, were generated.
The include/EditView/EditView.tpl has been overwritten by the themes/suiteP/include/EditView/EditView.tpl.
This SmartyTemplate calls tab_panel_content.tpl in the same folder... Well, as I'm using SuitePImproved this wasn't true, suitePImproved/include/EditView/EditView.tpl was loading suiteP/include/EditView/tab_panel_content.tpl so that had to be fixed.
Anyway, in the tab_panel_content.tpl file you find tabindex=$tabindex 4 times, that $tabindexare replaced by:
$subfields.tabindex
$colData.field.tabindex
$colData.field.tabindex
$colData.field.tabindex
And this is working everywhere for me.
This change is not upgrade-safe because I didn't get loaded that tpl from the custom/themes... I'll come back later to fix that
Related
I am new to VBA and am currently still studying the most basic ideas of the language. I haven't gotten that far in my VBA Code studies to write the code I need by hand, so, in the mean time, I have been using the VBA Editor to enter Property Values via the Properties Window. This has been proving far more difficult than I anticipated. My Goal is to create a drop down list for a VBA Form. I understand one of my options is to reference a range of cells in my excel worksheet by inputting it into the value field located right of the ControlSource Property. My attempts to input the desired range always comes up with the same error:
Could not set the ControlSource Property. Invalid Property Value.
I have tried looking in the VBA Help files and even searched online. I haven't had any luck finding the proper syntax to enter into this field.
I am assuming I may run into similar issues as I try to set other property values through the Property Window. Thus, I am diligently studying my VBA courses so I can simply write the raw code. But that takes time and I need this form to work as soon as possible.
Is there anyone out there that wouldn't mind lending me their brain for a moment? I would be most grateful. Having this working would bring a lot of stress off of me.
Thanks for reading!
What tigeravatar mentioned, works fine for me, for the ComboBox as well for the ListBox.
If I enter =a1:b5 into the ComboBox' RowSource, I see the values of the cells if I open the form and the Combobox. Tigeravatar's notation with $ and sheet! may be more reliable for the productive version.
The RowSource is where the boxes get their displayed items from. The ControlSource is where the chosen value finally is linked to. So if I write just A10 to the ControlSource, then open the form, then pick a value, close the form, I see the chosen value filled to the Excelsheet field A10.
Sometimes it helps to start a fresh UserForm and to add some simple fresh controls. If you seek around, you will probably alter property values that influence the behaviour in an unexpected way, and then you get lost. I have tested with Office 2010. If you have another version, it may be important to forum readers to know.
In Articulate's Storyline product, how does one retrieve the total number of slides (or pages) in a storyfile or project?
There's not much documentation so it's kind of hard to figure out how to query common environment values like this. If we can get the total number of slides then we don't have to manually set a value for it.
One must manually set and update a variable to store the number of slides.
The most lengthy conversation on the matter seems to be found here at the Articulate forums.
In that thread the users and staff describe the need to manually define such a variable.
I asked the question on the official forum more directly here, and so far have not received a response.
Another poster at that forum mentioned using PHP to solve this problem, but unfortunately we can't add the requirement of PHP to the final product. I'm sure some server side language tricks might be used to solve this issue, but that also adds the dependency of a particular server-side language.
The Answer Mark gave is correct. So if you want to track the number of question slides in a quiz you would either hard code the value in a variable such as totalQuestions, or increment it as you go through each slide using adjust variable trigger. To call that value and display it on screen you would just add it to a text field and surround it with "%".
EG. "You have answered %Results.ScorePoints% out of %totalQuestions% questions correctly."
I find it rather pointless to hard code it since it's just as easy to put the value in the text field at the end. Using the increment method seems more logical because then you can add more question slides without having to adjust the variable or results screen each time.
I usually load frame.xml, browse for all slidelink tags and sort all slides by their Id.
Usually you get something like slideid=_player.5xoxGTW6QCh.6bmeRt3tCqP, where 5xoxGTW6QCh is the scene id and 6bmeRt3tCqP is the slide id. displaytext also gives you the slide title.
If you browse for slidetranscript and match the Id for each transcript you also get the slide notes.
Articulate 360 now has an internal (Built-in) variable for this and other counts. See Project.TotalSlides and Menu.TotalSlides
See https://community.articulate.com/series/articulate-storyline-360/articles/storyline-360-add-slide-numbers
Recently, I started noticing odd behavior with one of my continuous forms. It contains text boxes in the header which can be used to filter the list. For some reason, whenever this form is requeried, for example when a record is edited or added in another form, this form reverts to its unfiltered state.
I stepped through the code and played around with some variables in the immediate window. The filter is still there, it just isn't being applied. Setting Me.FilterOn = True does nothing, as it is already true. A work around is easy, I can set Me.Filter = Me.Filter, but I would like to find out what is causing this behavior in the first place.
I have other contiunous forms that work completely fine; requerying them does not do anything to the filter. I'm assuming I changed some setting on the problematic form, but I have no idea what. I compared all the settings between the two forms in the property window and found nothing. Does anyone have any idea what is causing this behavior?
Well I figured out what was wrong. I realized the query that the form was based on was a pass-through query. As soon as I changed it to a normal access query, the problem went away.
Unfortunately I had it as a pass-through query for a reason. Mircosoft Access doesn't like my join. Sometimes it throws me a join not supported error, and other times it just gives me screwed up results... Looks like I'll have to rethink this query.
In several recent answers I see this code given as the way to retrieve the currently selected value of a <select> tag:
el.options[el.selectedIndex].value
Whereas the MDN documentation says that the .value property of an HTMLSelectElement is equivalent ("The value of this form control, that is, of the first selected option.")
el.value
Is there some reason (old broken browsers?) why the longer version seems to be preferred?
To my best knowledge, the .value way has always worked.
There is actually an extra problem with the first one - what happens when the user has not yet selected an option? Then the .selectedIndex is -1, which will make your script crash.
So go with el.value
I am stumped beyond belief.
I have a select box being generated by the cakephp form helper. I am feeding it an array of options, and passing an empty value... pretty standard stuff.
However, my "empty" field is showing up at the very bottom of the list.. not the top. So when the field loads, it just defaults to the first option... which is not the "empty" option.
Not a whole lot of room for error on the code here..
echo $this->Form->input('whatever',array('empty'=>'Choose One','options'=>$categories));
The only small item that might be important, is that $categories is a multi-array, so the select box has optgroups & options.
Is there some quirk/bug out there that I do not know of that is trying to force me to sneak into my scotch supply a few hours ahead of schedule?
edit: using the latest release of cakephp 1.3.x
I think that I once had the same problem.
It turned out to be the data (options array).
Is there an option with an empty key? probably the last one then.
this lead to the scenario I remember and seems to be the exact same thing.
the form helper will override this empty key value pair then and not create a second one.
without more infos from your end this will be difficult to solve.