Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Activity for H_Hâ€
Type | On... | Excerpt | Status | Date |
---|---|---|---|---|
Answer | — |
A: How can I schedule a later task in Python? While the other answers rely on external programs, you can do the same inside python. Using `time.sleep()` If you don't need to do any other tasks during this 10 min. ``` #!/usr/bin/env python3 import time def doThisIn10min(): # Replace this with the function you need to do in 10min... (more) |
— | 9 months ago |
Answer | — |
A: How to convert Dos paths to Posix paths in Powershell TL;DR: Use `wslpath` and hope for the best. You can use it like this in Powershell: `wsl wslpath -u 'C:\\some\\path\\to\\folder\\or\\file.txt' ` Long answer Converting them is hard. There is windows tool `wslpath` for Windows with WSL, but that may not work in every case. There is also `wi... (more) |
— | 9 months ago |
Answer | — |
A: OpenGL: Pass a double vector from vertex shader to fragment shader Found a workaround: Instead of doing the calculating in the vertex shader, do it in the fragment shader. The precision error only occurs because the different vertexes have a `uv` value that is close together relative to the absolute value of `uv`. Which causes multiple fragments to have the same ... (more) |
— | 9 months ago |
Question | — |
OpenGL: Pass a double vector from vertex shader to fragment shader TL;DR: How to pass a interpolated `double` vector, such as a `dvec2`, from the vertex shader to the fragment shader? I have a vertex shader. In this the output variable `out vec2 uv;` is set. And i have a fragment shader, in this the (intperpolated) input variable `in vec2 uv;` is expected. This w... (more) |
— | 9 months ago |
Answer | — |
A: Is omitting braces for single statements bad practice? While there are already good answers, i want to give yet another reason to always use `{}`: Macros. Lets consider this code: ``` #include #define FOO(n) puts(n[1]); puts(n[0]); int main(int argc, char argv) { if(argc>1) FOO(argv); } ``` You may expect that the code insid... (more) |
— | 9 months ago |