Jump to content


  • Content count

  • Joined

  • Last visited

About wigglepixel

  • Rank
    Advanced Member

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    : Utrecht, The Netherlands

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks a lot @Starchy97 . I love hearing that stuff . The whole reason why I wrote these articles is exactly that; when I was searching for information about these subjects myself, there were a lot of pretty technical dry or incomplete documents out there which I could find. I was missing something a little bit more fun to read, a little bit more colorful and easier to grasp these pretty technical and complex subjects. Something more designer-friendly (although still pretty complex, but that unfortunately comes with the subject I'm afraid). And I liked to help others with understanding this a little better. So nice to hear it helped you! Spread the word so in the end we all understand color models, color spaces and gamma correction
  2. Very cool to see people on this forum are still reading the blogs about Color Models and Color Spaces (a lot) even a year later now! Thanks!
  3. Thanks @haakoo. Nice to read you like it. Four parts still to come
  4. Thanks @GarryP for your compliment and the hint on the PLATO project. Sounds interesting. If I have a little more time I'll take a closer look and listen at it.
  5. Yes!! Part 2 is (finally!) out in the open now! Hope you like it! There will be a new part in between a month and a few months from now, as soon as possible, but quality content. Already working on it. In the end there will be 6 parts in total. Collect them all ! This time with an oldfashioned game inside that fits this period of history! Enjoy! English: History Interactive Computer Graphics - Part 2 Dutch: Geschiedenis Interactieve Computergraphics - Deel 2 @Alfred @Madame @Roger C @GarryP @Wosven @A_B_C @WatcherMagic @John Rostron @Renzatic @dutchshader
  6. Well, it's been a while, I've been very busy last months and I take writing blogs seriously and like to serve quality content. So sorry you had to wait sooo long, but the second part of the series will go live soon! ...And there will be a little oldfashioned GAME inside! (and it's not or ) @Alfred @Madame @Roger C @GarryP @Wosven @A_B_C @WatcherMagic
  7. After setting up a keyboard shortcut by hitting the a numerical key on the top of a standard querty keyboard in the keyboard shortcuts settings panel, both the numericalkey as well as the numpadkey representing the same number trigger this new shortcut. For example, pressing the '1'-key on the top of the keyboard together with alt to assign a shortcut results in the same keystroke as pressing the 'numpad1'-key together with the same alt-key. This is not what I would expect, because these are two different keys with no technical connection. Treating both keys as the same limits the amount of keystrokes we can assign. It's also errorprone, because we don't expect the alt+'numpad1' to trigger an action we assigned the alt+'1' (1 on the top of the keyboard). So it seems like Affinity doesn't store the key-code, but the key-value to bind a keyboard shortcut. But it should store the key-code instead to assign the right key only. [edit] Another problem caused by this is what I'm facing right now: I have a rotation assigned to Alt+2 (addressing the regular '2' key on the top of the keyboard). But when I'm in a textframe and want to enter a special character by using an alt code sequence (so while holding Alt hitting a code-sequence like numpad-0, numpad-2, numpad-3, numpad-3 to have a 'é'-symbol) the alt-way to enter a symbol doesn't work anymore AND the canvas will rotate. And that's obviously not what should happen here. I wouldn't be surprised if there's a connection between this one and the no-difference-between-alt-keys Issue I reported earlier. Maybe the same solution could fix both? That would be nice! Thanks in advance!
  8. Seriously? This is no hardware issue and has nothing to do with the keyboard hardware nor driver. We can tell, because we can see clearly in the interface that Affinity knows the difference between the left and right alt (it's not showing a warning symbol when we use different alt keys), but just doesn't show the right name for the key (leftAlt / rightAlt (or AltGr)). It's obviously happening on several totally different windows machines (I alone saw it on all three systems I work on, which are totally different both in hardware, age, as in configuration, and it's also confirmed by @walt.farrell as you could've read here). This is clearly a problem in the Affinity software, so I'm very surprised by your reactions (and that you didn't remove the [fixed] from the title). Could it be you perhaps misunderstood my post? Could you please post a video to show us it's working on a genuine Windows machine (so no Virtual Machine, or the Mac-configuration you were talking about before, but a PC (no Mac) with Windows)?
  9. Gabriel, the brand or model of the keyboard is irrelevant information to solve this issue. Like I wrote in the opening post Affinity already knows which alt is pressed. This has nothing to do with hardware. It's just the Affinity software not showing the right label-texts. And that's certainly an easy thing to fix for a developer by just looking at the codebase alone. Maybe you could remove the [fixed] label in the title, because it's obviously not fixed yet.
  10. wigglepixel

    [AD] [AP] Misc illustrations

    These animal-cars are great! Great idea!
  11. Thanks for your confirmation and try to help @adi. I understand it's easy to setup a document with a grid indeed, but found that site and just tested it out for fun and than found this bug so reported it. Could be a nice online tool to create a grid file though, well, if it worked