Version 7.1.0 And, yes, any project. It used to work, and I used it a lot. Now, nothing. I've resorted to using a different editor. Every now and then my fingers slip while typing on the keyboard, and either that puts the IDE into some weird mode -- like the time it got stuck in block-selection mode...

Yeah, I know. That was my point. When searching for 24F support, I wondered if "dsPIC" still implied "24F" within the context of the topic of this post.

Hi, My installation of mikroC Pro for dsPIC has developed a "Negative workflow" behavior. I open the "Find In Files" dialog, enter a "Text to find", and then I hit "OK". After that, NOTHING! The dialog vanishes. There is no sign of any search results, ANYWHERE. Not even an indication of "No search h...

So, the real issue is with the documentation. Instead of "constant", it should say "literal constant" or merely "literal". The omission of that qualifier gave me the impression the Delay_ms() function was capable of more than it is, which was a time waster! One simple word would have saved me consid...

You nailed it. My goal is to implement a "low-level" error indication as a back up for my higher level UART error handler. Errors are also displayed on an LCD on the "console". The idea is to have some form of error indication in the absence of access to the higher level indicators. And, I thought o...

I did all of that -- as reported in my original post <see above>. And, yes, I know the difference between Delay_ms() and VDelay_ms() -- also indicated in my original post <see above>.

Try removing the 'L' from the format specification: The 'L' is only specified for integer types:

The optional characters l or L may immediately precede conversion_type to respectively specify long versions of the integer types d, i, u, o, x, and X.

The following code causes a "376 Integer const expected" compiler error message: // FYI I trimmed this code down to the essentials to showcase my issue. const unsigned int ERR__ALL_FUBAR = 15; sbit pin_o_error at LATA7_bit; void handle_error(const unsigned int); void main() { handle_error(ERR__ALL_F...

Unofficial third reason: I don't know if my case is unique, but MikroC, both PIC and dsPIC, have crashed A LOT!! And, it seemed like you guys placed most of your focus on developing your "Click" products, rather than supporting the Mikro compilers. So, if I'm going to shell out $30 a month, I'd lik...

Also, I hope it will tell me if certain [long requested] features are finally implemented, like the ability to code the configuration "fuses", the preservation of header file paths in a project, implementation of the inline keyword, addition of bit and sbit arrays, advanced compiler features like t...

I'm holding off on shelling out the $$$ for Necto for two reasons: 1) I want to see a Migration Guide for porting my large body of code from MikroC-PRO forPIC and dsPIC. I want to see how much effort it will take to port my code to the new environment. Also, I hope it will tell me if certain [long r...

I guess this doesn't come up very often, but... I would also like an answer to this. I tried: *.c*.h ... NOPE! *.h,*.c ... NOPE! *.h;*.c ... NOPE! *.h|*.c ... NOPE! \*\.[hc] ... NOPE! \*\.(h|c) ... NOPE! *.[hc] ... NOPE! *.(h|c) ... NOPE! Why do I want this? Because if I use *.*, I get results from ...

Yup! I saw that. And, none of that has to do with PIC24. So, what's up with that?

[Unless, the same arcane naming "dsPIC" refers to PIC24?!? I mean, am I supposed to assume dsPIC refers to "dsPIC/PIC24"?!]

My mother taught me to NEVER assume!

I apologize if this has already been covered -- my forum searches came up empty. Am I missing something? I currently own licenses for MikroC PRO for PIC and dsPIC, and I'm wondering about his new " AI " offering [what is that? Artificial Intelligence ?!?], but I paged through the Supported Devices a...

Cool, thank you.

May I suggest that you add that to the documentation?