One of these are the buttons to view your trimp stats and the enemy's in more deapth (where it starts the map name, the type of enemy etc), another are the save config stats in the map chamber, indeed its a bit odd since the saving perk options have no issues with lables.Īs for testing, feel free to drop the link and I'll be glad to give it a go. Lastly, I have run into a couple of things in the game which are simply not labeled, or where it is not exactly %100 clear what does what. I like the idea of enemy trimp stats quickly accessible via headings, as I said currently while it lists my min/max attack and block I don't seem to be able to see my trimps actual hp. Speaking of finishing zones, it might be nice to have a "zone complete" type of text in the log, just to give you a sense of completion, especially if you've tabbed out of the window for a while. Suggestions of headings and buttons are definitely good ones, and I like the idea of specific alerts that would be spoken directly, indeed you could consider adding a couple of extra togglable alert categories for story text, unlocks and finishing a zone.
#TRIMPS GAME REVIEW UPGRADE#
Speaking of the map, I don't know if there is a graphical representation which square your trimps are currently on, as I said earlier in the topic, its possible to review the map by going up from the "save" option after hitting T, but knowing where you are might be good, since it'd let you know if there was a good upgrade coming up and whether to push forward take your fragments and upgrade hunting. L will also get me to the top row of the map, and its often quicker to go from there to find links to go to the map chamber, check out the current square etc. This means I can then hit up arrow to go to the bottom of the log and read what's going on,Īrrow down a line or two to job assignments, buildings etc, then hit k to go to the link for the "custom" box and read down from there.Īs for the log itself, the events are read fine on my end, however since the log doesn't print each event on a separate line occasionally I need to read a line or two.
To read the log I hit L until I get to the "all" tab just under the building cue. There are also times I use the find text feature, by hitting NvdA f3, in ~Trimps I tend to do this when I want to buy a specific building upgrade like a hotel.ģ: As of now, the key I use most in trimps is the l key to jump between lists. In a more complex page, or if other navigation features aren't available yes, I'll usually start with arrow keys, however for me its not so much a question of working out the layout on a visual level as of finding a set of landmarks to the things I want to find on the page, for example, often information is located under or above a link and its easier to find that link and go up or down than try to scan down from somewhere else, or use a combination of landmark keys in conjunction, EG hitting h for a certain heading and then going down from that via links. If its a form I'll look for form controls and fields, if an informational set of links I'll go by link or the good old tab key. If I am just having a quick glance at a blog post or something that I know to have an article, wiki like structure I'll probably just hit h to find the thing I want and read down from there. Additionally, SRPE is a simple and low-cost method that might be used for TL monitoring in handball.Wow that sounds awesome and goes way beyond what I was thinking.ġ: Yes, while there are other screen readers than NVdA they do use similar keys for web navigation and track similar elements, indeed web nav methods with screen readers are sort of standardised these days.Ģ: Probably something of an individual matter and a matter of experience using screen readers, but for me at least it depends upon what I'm going to a site for. The results suggest that different constructs seem to be measured by each load model. Shared variances of 13–35% were observed between TL methods comparisons. A moderate correlation was observed for Edwards’ Trimp vs. A large correlation was found between Edwards’ Trimp and distance covered (r=0.59). An oscillatory feature was observed for the three methods of TL assessment (SRPE: 383☑59 A.U., Edwards’ Trimp: 252☗1 A.U., total distance: 3997☑291 m). Internal load models based on SRPE and Edwards’ Trimp were calculated. Distance covered, heart rate and session rating of perceived exertion were recorded during 12 training sessions in 14 youth women handball athletes (16.9☑.1 years). This study examined the association between different methods for training load (TL) monitoring during youth handball training.
0 kommentar(er)
