strToHex ( string to it's hex representation as string)Integer-to-hex string generatorConvert hex string to byte arrayString representation of TreeSimple string inverter programSimple string repeater programGeneric Pairing Heap PerformanceHex-string representation of a byte arrayConvert hex color string to SDL ColorC binary number converter (Hex and Decimals)Convert string of hex into vector of bytes

Why dont electromagnetic waves interact with each other?

Show that if two triangles built on parallel lines, with equal bases have the same perimeter only if they are congruent.

Adding span tags within wp_list_pages list items

Theorems that impeded progress

Approximately how much travel time was saved by the opening of the Suez Canal in 1869?

Fencing style for blades that can attack from a distance

I’m planning on buying a laser printer but concerned about the life cycle of toner in the machine

How to find program name(s) of an installed package?

What typically incentivizes a professor to change jobs to a lower ranking university?

Is a tag line useful on a cover?

Is this a crack on the carbon frame?

What does it mean to describe someone as a butt steak?

Why don't electron-positron collisions release infinite energy?

What do you call a Matrix-like slowdown and camera movement effect?

Why can't I see bouncing of a switch on an oscilloscope?

Problem of parity - Can we draw a closed path made up of 20 line segments...

tikz: show 0 at the axis origin

To string or not to string

Email Account under attack (really) - anything I can do?

How is it possible to have an ability score that is less than 3?

How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?

TGV timetables / schedules?

What's the output of a record cartridge playing an out-of-speed record

Today is the Center



strToHex ( string to it's hex representation as string)


Integer-to-hex string generatorConvert hex string to byte arrayString representation of TreeSimple string inverter programSimple string repeater programGeneric Pairing Heap PerformanceHex-string representation of a byte arrayConvert hex color string to SDL ColorC binary number converter (Hex and Decimals)Convert string of hex into vector of bytes






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1












$begingroup$


I want to convert strings to it's hex representation as string too (like hex dump programs), for example "abz" to "61627A"



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A









share|improve this question











$endgroup$







  • 2




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    1 hour ago










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    21 mins ago

















1












$begingroup$


I want to convert strings to it's hex representation as string too (like hex dump programs), for example "abz" to "61627A"



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A









share|improve this question











$endgroup$







  • 2




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    1 hour ago










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    21 mins ago













1












1








1





$begingroup$


I want to convert strings to it's hex representation as string too (like hex dump programs), for example "abz" to "61627A"



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A









share|improve this question











$endgroup$




I want to convert strings to it's hex representation as string too (like hex dump programs), for example "abz" to "61627A"



char * strToHex( char * str )

int length = strlen ( str );
char * newStr = malloc( length * 2 );
if ( !newStr ) shutDown ( "can't alloc memory" ) ;

for ( int x = 0; x < length; x++)
char y = str[ x ];
sprintf ( newStr + x * 2, "%02X", y );

return newStr;



ShutDown definition is omitted here, it is a function that calls perror and exit()



I designed strToHex to be used like



char * str = "abcdefghijklmnopqrstuvwxyz";
char * hex = strToHex(str);
printf("%sn",hex);
//outputs : 6162636465666768696A6B6C6D6E6F707172737475767778797A






beginner c strings






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 23 mins ago









esote

2,93111038




2,93111038










asked 2 hours ago









Accountant مAccountant م

1827




1827







  • 2




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    1 hour ago










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    21 mins ago












  • 2




    $begingroup$
    I'd be really interested to see what shutdown(char* msg) does.
    $endgroup$
    – pacmaninbw
    1 hour ago










  • $begingroup$
    In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
    $endgroup$
    – Neil Edelman
    21 mins ago







2




2




$begingroup$
I'd be really interested to see what shutdown(char* msg) does.
$endgroup$
– pacmaninbw
1 hour ago




$begingroup$
I'd be really interested to see what shutdown(char* msg) does.
$endgroup$
– pacmaninbw
1 hour ago












$begingroup$
In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
$endgroup$
– Neil Edelman
21 mins ago




$begingroup$
In the use case that was provided, since you can effectively predict the size, I would think it would be more natural to have a string buffer and the size passed in instead of creating it dynamically.
$endgroup$
– Neil Edelman
21 mins ago










1 Answer
1






active

oldest

votes


















2












$begingroup$

Formatting



Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



int *a, b;


Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



int length = strlen ( str );
char * newStr = malloc (length * 2 );
if ( !newStr) shutDown ( "can't allocate memory" ) ;


Becomes:



int const len = strlen(str);
char *const new_str = malloc(len * 2);

if (new_str == NULL)
shutDown("can't allocate memory");



Error checking



Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




Return Value



The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




So by returning NULL we account for the case where malloc(3) returns NULL on success.



if (new_str == NULL) 
shutDown("can't alloc memory");



Becomes:



if (new_str == NULL) 
return NULL;



If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



Looping



Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



Using i rather than x is more common for looping variables.



The y variable isn't needed. You can simply use str[i] in its place.



In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



Conclusion



Here is the code I ended up with:



#include <stdio.h>
#include <stdlib.h>
#include <string.h>

char *
str_to_hex(char const *const str)

size_t const len = strlen(str);

char *const new_str = malloc(len * 2);

if (new_str == NULL)
return NULL;


for (size_t i = 0; i < len; ++i)
sprintf(new_str + i * 2, "%02X", str[i]);


return new_str;


int
main(void)

char *str = "abz";
char *hex = str_to_hex(str);

if (hex == NULL && strlen(str) != 0)
/* error ... */


printf("%sn",hex);

free(hex);



Hope this helps!






share|improve this answer











$endgroup$













    Your Answer





    StackExchange.ifUsing("editor", function ()
    return StackExchange.using("mathjaxEditing", function ()
    StackExchange.MarkdownEditor.creationCallbacks.add(function (editor, postfix)
    StackExchange.mathjaxEditing.prepareWmdForMathJax(editor, postfix, [["\$", "\$"]]);
    );
    );
    , "mathjax-editing");

    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "196"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f216992%2fstrtohex-string-to-its-hex-representation-as-string%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    2












    $begingroup$

    Formatting



    Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



    I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



    int *a, b;


    Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



    int length = strlen ( str );
    char * newStr = malloc (length * 2 );
    if ( !newStr) shutDown ( "can't allocate memory" ) ;


    Becomes:



    int const len = strlen(str);
    char *const new_str = malloc(len * 2);

    if (new_str == NULL)
    shutDown("can't allocate memory");



    Error checking



    Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



    Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




    Return Value



    The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




    So by returning NULL we account for the case where malloc(3) returns NULL on success.



    if (new_str == NULL) 
    shutDown("can't alloc memory");



    Becomes:



    if (new_str == NULL) 
    return NULL;



    If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



    Looping



    Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



    Using i rather than x is more common for looping variables.



    The y variable isn't needed. You can simply use str[i] in its place.



    In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



    Conclusion



    Here is the code I ended up with:



    #include <stdio.h>
    #include <stdlib.h>
    #include <string.h>

    char *
    str_to_hex(char const *const str)

    size_t const len = strlen(str);

    char *const new_str = malloc(len * 2);

    if (new_str == NULL)
    return NULL;


    for (size_t i = 0; i < len; ++i)
    sprintf(new_str + i * 2, "%02X", str[i]);


    return new_str;


    int
    main(void)

    char *str = "abz";
    char *hex = str_to_hex(str);

    if (hex == NULL && strlen(str) != 0)
    /* error ... */


    printf("%sn",hex);

    free(hex);



    Hope this helps!






    share|improve this answer











    $endgroup$

















      2












      $begingroup$

      Formatting



      Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



      I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



      int *a, b;


      Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



      int length = strlen ( str );
      char * newStr = malloc (length * 2 );
      if ( !newStr) shutDown ( "can't allocate memory" ) ;


      Becomes:



      int const len = strlen(str);
      char *const new_str = malloc(len * 2);

      if (new_str == NULL)
      shutDown("can't allocate memory");



      Error checking



      Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



      Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




      Return Value



      The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




      So by returning NULL we account for the case where malloc(3) returns NULL on success.



      if (new_str == NULL) 
      shutDown("can't alloc memory");



      Becomes:



      if (new_str == NULL) 
      return NULL;



      If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



      Looping



      Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



      Using i rather than x is more common for looping variables.



      The y variable isn't needed. You can simply use str[i] in its place.



      In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



      Conclusion



      Here is the code I ended up with:



      #include <stdio.h>
      #include <stdlib.h>
      #include <string.h>

      char *
      str_to_hex(char const *const str)

      size_t const len = strlen(str);

      char *const new_str = malloc(len * 2);

      if (new_str == NULL)
      return NULL;


      for (size_t i = 0; i < len; ++i)
      sprintf(new_str + i * 2, "%02X", str[i]);


      return new_str;


      int
      main(void)

      char *str = "abz";
      char *hex = str_to_hex(str);

      if (hex == NULL && strlen(str) != 0)
      /* error ... */


      printf("%sn",hex);

      free(hex);



      Hope this helps!






      share|improve this answer











      $endgroup$















        2












        2








        2





        $begingroup$

        Formatting



        Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



        I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



        int *a, b;


        Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



        int length = strlen ( str );
        char * newStr = malloc (length * 2 );
        if ( !newStr) shutDown ( "can't allocate memory" ) ;


        Becomes:



        int const len = strlen(str);
        char *const new_str = malloc(len * 2);

        if (new_str == NULL)
        shutDown("can't allocate memory");



        Error checking



        Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



        Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




        Return Value



        The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




        So by returning NULL we account for the case where malloc(3) returns NULL on success.



        if (new_str == NULL) 
        shutDown("can't alloc memory");



        Becomes:



        if (new_str == NULL) 
        return NULL;



        If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



        Looping



        Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



        Using i rather than x is more common for looping variables.



        The y variable isn't needed. You can simply use str[i] in its place.



        In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



        Conclusion



        Here is the code I ended up with:



        #include <stdio.h>
        #include <stdlib.h>
        #include <string.h>

        char *
        str_to_hex(char const *const str)

        size_t const len = strlen(str);

        char *const new_str = malloc(len * 2);

        if (new_str == NULL)
        return NULL;


        for (size_t i = 0; i < len; ++i)
        sprintf(new_str + i * 2, "%02X", str[i]);


        return new_str;


        int
        main(void)

        char *str = "abz";
        char *hex = str_to_hex(str);

        if (hex == NULL && strlen(str) != 0)
        /* error ... */


        printf("%sn",hex);

        free(hex);



        Hope this helps!






        share|improve this answer











        $endgroup$



        Formatting



        Most C formatting guides do not include spaces around the arguments to function calls, nor the expressions within an if-statement. For an example of a C style most C programmers would find acceptable, see OpenBSD's style(9) manual.



        I choose to associate * with the variable name, rather than floating between the type and name. This disambiguates the following example:



        int *a, b;


        Here, a is a pointer to an integer, but b is only an integer. By moving the asterisk next to the name, it makes this clearer.



        int length = strlen ( str );
        char * newStr = malloc (length * 2 );
        if ( !newStr) shutDown ( "can't allocate memory" ) ;


        Becomes:



        int const len = strlen(str);
        char *const new_str = malloc(len * 2);

        if (new_str == NULL)
        shutDown("can't allocate memory");



        Error checking



        Rather than calling shutDown() and exit()ing the program, you should instead return an error value which can be checked by the caller of str_to_hex(). Because you return a pointer, you can return NULL to indicate an error occurred and the caller should check errno.



        Likewise, on some systems your program can incorrectly exit when length == 0. If we look at the manual page for malloc(3):




        Return Value



        The malloc() and calloc() functions return a pointer to the allocated memory that is suitably aligned for any kind of variable. On error, these functions return NULL. NULL may also be returned by a successful call to malloc() with a size of zero, or by a successful call to calloc() with nmemb or size equal to zero.




        So by returning NULL we account for the case where malloc(3) returns NULL on success.



        if (new_str == NULL) 
        shutDown("can't alloc memory");



        Becomes:



        if (new_str == NULL) 
        return NULL;



        If you choose, you can also check if str is NULL before calling strlen(). This is up to you, and it's not uncommon in C to ignore this case and leave it as user error.



        Looping



        Use the size_t type in your loop rather than int. size_t is guaranteed be wide enough to hold any array index, while int is not.



        Using i rather than x is more common for looping variables.



        The y variable isn't needed. You can simply use str[i] in its place.



        In terms of performance there's likely a faster option than using sprintf(). You should look into strtol(3).



        Conclusion



        Here is the code I ended up with:



        #include <stdio.h>
        #include <stdlib.h>
        #include <string.h>

        char *
        str_to_hex(char const *const str)

        size_t const len = strlen(str);

        char *const new_str = malloc(len * 2);

        if (new_str == NULL)
        return NULL;


        for (size_t i = 0; i < len; ++i)
        sprintf(new_str + i * 2, "%02X", str[i]);


        return new_str;


        int
        main(void)

        char *str = "abz";
        char *hex = str_to_hex(str);

        if (hex == NULL && strlen(str) != 0)
        /* error ... */


        printf("%sn",hex);

        free(hex);



        Hope this helps!







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited 13 mins ago

























        answered 27 mins ago









        esoteesote

        2,93111038




        2,93111038



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Code Review Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            Use MathJax to format equations. MathJax reference.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fcodereview.stackexchange.com%2fquestions%2f216992%2fstrtohex-string-to-its-hex-representation-as-string%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Are there any AGPL-style licences that require source code modifications to be public? Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?Force derivative works to be publicAre there any GPL like licenses for Apple App Store?Do you violate the GPL if you provide source code that cannot be compiled?GPL - is it distribution to use libraries in an appliance loaned to customers?Distributing App for free which uses GPL'ed codeModifications of server software under GPL, with web/CLI interfaceDoes using an AGPLv3-licensed library prevent me from dual-licensing my own source code?Can I publish only select code under GPLv3 from a private project?Is there published precedent regarding the scope of covered work that uses AGPL software?If MIT licensed code links to GPL licensed code what should be the license of the resulting binary program?If I use a public API endpoint that has its source code licensed under AGPL in my app, do I need to disclose my source?

            2013 GY136 Descoberta | Órbita | Referências Menu de navegação«List Of Centaurs and Scattered-Disk Objects»«List of Known Trans-Neptunian Objects»

            Button changing it's text & action. Good or terrible? The 2019 Stack Overflow Developer Survey Results Are Inchanging text on user mouseoverShould certain functions be “hard to find” for powerusers to discover?Custom liking function - do I need user login?Using different checkbox style for different checkbox behaviorBest Practices: Save and Exit in Software UIInteraction with remote validated formMore efficient UI to progress the user through a complicated process?Designing a popup notice for a gameShould bulk-editing functions be hidden until a table row is selected, or is there a better solution?Is it bad practice to disable (replace) the context menu?