Why Keyboard Users Can’t Scroll Your Overflow Containers, by @csstricks:
https://css-tricks.com/why-keyboard-users-cant-scroll-your-overflow-containers/
When a keyboard user Tabs into the table, its focus lands on a cell. Then they press the arrow keys to read across the row but nothing happens. Your screen reader users never noticed because they navigate the accessibility tree, not the scroll container.
THANK YOU ALL!!! - what errors should I check for and handle?
Thank you all for your kind, patient and educative responses when I obnoxiously post amateur questions! 💙 While I cannot make any promises because of how my brain works, I am almost ready to continue reading *The C Programming Language, 2nd Edition”. I just want to experiment a little bit with error handling, specifially how to handle wrong input (char VS. int, etc.) and also to learn to indentify code that runs the risk of overflow/underflow.
Question: what errors do you recommend checking for and handling?
Meanwhile, thank you all! 🥰
Frontend Dogma
printf("%s", name);#include <stdio.h>
//Function declarations
int newPin();
int checkPin(int i);
//Program that prompts for, verifies and saves pins temporarily into an array
int main() {
//New pin
int pin = 0;
//History
int history[10] = {0,0,0,0,0,0,0,0,0,0};
int history_limit = 10;
int history_index = 0;
printf("Hello there! What would you like to do? (V)iew your saved pins, (S)ave a new pin or (E)xit: ");
int choice = 0;
while ((choice = getchar()) != EOF) {
switch (choice) {
case ('V'): { //Display saved pins
printf("\nYour saved pins are:\n\n");
for (int i = 0; i < history_limit; i++) printf("%d\n", history[i]);
printf("\nWhat would you like to do next? (V)iew your saved pins, (S)ave a new pin or (E)xit: ");
break;
}
case('S'): { //Prompt for and verify newly entered pin
pin = newPin();
if (checkPin(pin) == pin) {
history[history_index] = pin;
history_index++;
if (history_index >= history_limit) history_index = 0;
}
break;
}
case ('E'): goto EXIT; //Terminate program
}
}
EXIT: printf("\nGoodbye!\n");
return 0;
}
//Function definitions
//Prompt user to enter a new pin
int newPin() {
int pin = 0;
printf("This enter your pin: ");
scanf("%d", &pin);
getchar();
return pin;
}
//Verify newly entered pin
int checkPin (int i) {
int check = 0;
printf("Confirm your new pin: ");
while((scanf("%d", &check)) != EOF) {
if (check != i) printf("Mismatch! Confirm your new pin: ");
else if (check == i) {
printf("Success! Your new pin is %d. What would you like to do next? (V)iew your saved pins, (S)ave a new pin or (E)xit: ", i);
goto EXIT;
}
}
EXIT: return i;
}
//TODO
//Error handling (overflow, input data type, other?)
In Java unterscheidest du grob zwischen primitiven Datentypen und Referenztypen. Primitive Typen sind die Basis: Sie speichern den Wert direkt, ohne Objekt-Hülle. Das macht sie schnell, vorhersehbar und speichereffizient. Wichtig ist dabei: Die Größe der primitiven Typen ist in Java fest definier
https://magicmarcy.de/datentypen-in-java-ohne-stolperfallen
#DAtentypen #Java #Stolperfallen #2038 #Overflow #int #Integer #String #float #double #BigDecimal #Wertebereiche #Programming
In Java unterscheidest du grob zwischen primitiven Datentypen und Referenztypen. Primitive Typen sind die Basis: Sie speichern den Wert direkt, ohne Objekt-Hülle. Das macht sie schnell, vorhersehbar und speichereffizient. Wichtig ist dabei: Die Größe der primitiven Typen ist in Java fest definiert und hängt nicht vom Betriebssystem ab. Genau diese Festlegung macht Code auf verschiedenen Plattformen so stabil.
[C programming] Why and how is the allocated bytes affecting these unexpected behaviors?
[C] What is the relationship between string length, allocated memory size and overflow?
CBC Calgary
CBC Top Stories
magicmarcy
Global News
Global News Winnipeg
Global News Environment