User forums > Using Code::Blocks
Code Hinting but not Completion
pieman:
Hey.
Hello?
--- Quote ---Frankly, it's just a waste of screen real estate to have a window permanently open to display contextual info like this.
--- End quote ---
NO! I SAID A TAB, MULTIPLE TIMES. A tab integrated into the logs panel. It makes perfect sense. After you get your build messages, you'll be pushing through code using the build messages. Once you've fixed your code to be however you want it fixed, then you'll possibly be working on new, novel code. In that circumstance, it's appropriate to switch from build messages to the "contextual info" while developing new stuff, rather than fixing issues named in the build messages!
What the fuck people..
A tab. A tab. A tab! How do you manage to concede this and unmistakable simple design decision?
BUILD PROGRAM.
LOOK, BUILD MESSAGES.
ADDRESS BUILD MESSAGES.
GOOD.
NOW I HAVE THOUGHTS ON SOMETHING NEW I NEED TO WORK ON.
SWITCH FROM BUILD MESSAGES TAB TO SYMBOLS LIST TAB.
NOW THE BUILD MESSAGES TAB HAS BEEN REPLACED WITH THE SYMBOLS LIST TAB.
I DO NOT NEED THE BUILD MESSAGES TAB. IT HAS BEEN APPROPRIATELY REPLACED.
SCREEN SPACE CONSERVED.
Freaking shit.
pieman:
Game Maker's code editor lacked line numbers. Have you mistaken that screenshot image as like a scratch pad window thing? It's not. It's a code editor.
dmoore:
Let me fix that for you... :D
--- Quote from: pieman on April 11, 2014, 08:25:33 pm ---What the fuck people..
BUILD PROGRAM.
LOOK, BUILD MESSAGES.
ADDRESS BUILD MESSAGES.
GOOD.
NOW I HAVE THOUGHTS ON SOMETHING NEW I NEED TO WORK ON.
F2 - HIDE LOGS AND OTHERS, ENJOY IMPRESSIVE VISTA OF CODE WITH CODECOMPLETION POPUPS RIGHT WHERE YOU ARE TYPING.
SCREEN SPACE MAXIMIZED!
--- End quote ---
Also on a wide screen, the placement on the left side of symbols is probably a better use of screen real estate than displaying that info below.
pieman:
Actually, I do that indeed. I use F2 frequently (and I sometimes pin the logs panel to the right), but I'm saying, if you're keeping the logs panel open anyway, it may as well be more useful when you're not tracing the build messages.
It makes sense to me to have the feature I suggested paired in the same neighborhood as build messages, since build messages are attached to symbols and line numbers (they're a browsing solution). When I write new code, I don't want to browse, I want to reference (without browsing; need to focus on code HERE)! It's quite a nice duality, I think.
Code completion won't appear if a function (or whatever) has already been written. Then I must visit declarations. This wastes my time quite effectively. It makes it somewhat more difficult to focus on whatever I'm programming.
.. and it fucks up what I'm typing and when I'm typing I won't notice the evil shit popup out of hell and then rape my children before I finish typing. That's why I leave code completion disabled.
BlueHazzard:
--- Quote from: pieman on April 11, 2014, 08:48:22 pm ---Code completion won't appear if a function (or whatever) has already been written. Then I must visit declarations. This wastes my time quite effectively. It makes it somewhat more difficult to focus on whatever I'm programming.
.. and it fucks up what I'm typing and when I'm typing I won't notice the evil shit popup out of hell and then rape my children before I finish typing. That's why I leave code completion disabled.
--- End quote ---
actually not, just move the mouse cursor in top of the function and a popup will show you your info...
and why you don't ignore the cc popup?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version