LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Carriage return broken for comments

Solved!
Go to solution

I'm not sure how I did.  But now I can no longer use a carriage return in a comment.  

 

I've restarted LabVIEW.  I've rebooted my PC.  

 

But now, instead of moving to the next line when I hit retrun while typing a comment, it just closes it.  Probably not a big deal.  But I'm right in the middle of a super tight deadline, and now commenting is going to take me way longer.  

 

How can I fix this?

---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 1 of 5
(2,820 Views)
Hit ctrl-Enter. Or, There's an option under Environment to make Enter go to the next line or stop editing.  "End text entry with enter" key is hte option.
--
Tim Elsey
Certified LabVIEW Architect
Message 2 of 5
(2,817 Views)

Thanks for your reply.  But that wasn't it. 

 

Ctrl-enter does the exact same thing as enter.  And enviroment settings are unchecked to end text entry with  enter key. 

 

Here's a weird one tho':  If I check that box, then ctrl-enter works to move to next line.  

 

I hope I don't have to re-install labview just get my default behaviour back. 

---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 3 of 5
(2,811 Views)
Solution
Accepted by topic author pallen

Patrick,

 

is there a difference between the enter key and the numpad enter key?

Where are you creating those free labels (FP or BD)?

Do you have any key-locks active (numlock/capslock)?

 

hope this helps,

Norbert

 

[Edit] Since you already rebooted your PC: What happens if you use another keyboard? 

Message Edited by Norbert B on 11-23-2009 08:51 AM
Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 4 of 5
(2,807 Views)

Weird.

 

I was just going to start poking at those things.  

 

It looks like the Num lock was doing it.  But I'm pretty sure I've normally got the num lock on, and this didn't start up until I poked at the size to text setting this morning.  Then the behavior completely changed.

 

It does seem to be working now, and that's the main thing.  Thanks very much for the reply!

 

---------------------
Patrick Allen: FunctionalityUnlimited.ca
0 Kudos
Message 5 of 5
(2,801 Views)