I took back the time to set aside some time to develop in C again, and of course fired up my trusty codeclap debugger :D (and it did helped me tremendously on some quirky parsing bugs I had.)
As I remembered the ergonomy tended to give me some friction, so I used to opportunity to be "fresh again" on codeclap to record myself using it for the first 25 minutes. Here are the notes I had :
By the way, I'm on manjaro with i3wm as a window manager. And this was launched on a fresh codeclap extraction with last version to date on itch.io
- For me, police is blurry on launch. I have a 23" 1920x1020.
- I wanted to correct/arrange bluriness by using the custom dpi value. The slider is nice, but it can be hard to set an exact value. It would be nice to have a text field next to the slider.
That being said, the fact that the first thing on launch is the choose your dpi screen means that you know about the problem and that you did what is necessary to mitigate it until it's correct everytime.
- possibility to search (Ctrl-f) into the file. maybe the feature is there, but I didn't found it, event on the keybinding tab
on the expression window :
- possibility to display dynamic array like static array (on the screen capture, vertices.data
is an array allocated with malloc and I can't found how to display it like the static array cubePosition)
-the fact that the expression we are editing is highlighted or not is not obvious. thus I often get suprised by the fact that pressing a letter erase the whole expression. I also can't get the intuition on when the expression will be highlighted or not
- Control + left/right arrow should make me move word by word. exact behavior tends to depend on editor whether or not it should stop on camelCase or not, but on "|vector.data
" the cursor should advance to the dot I think (before or after) "vector.|data"
- when starting to type an expression, some autocompletion are presented below, pressing down stops the editing of expression and I have to click back on the expression I was editing. I did found an option to change this behavior, but i strongly thinks this should be the default to avoid forcing the user to take the mouse on the auto-complete window to give it focus before selecting the matching autocomplete. (but maybe I missed a better workflow)
Here are most of what i extracted for the 25 minutes footage.
Sorry to come like this with a list of requests. If the footage in itself interests you, I can put it up somewhere and give you a link to download it. I still feel very empowered by codeclap on my C programming, but I guess I always want more ^^
By the way, I found on your bug tracked that there seems to be some awesome activity already boilling. I can't wait for the next release :D