Keyboard Shortcut and Menu Bugs in AVR Studio 4

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Apologies if any (or even all) of these have been reported before.

1) Customized keyboard shortcut for Build command not honoured

To reproduce, remove F5 from the RUN command and assign it to the Build command. The accelerator shortcut shown in the Build dropdown menu is still F7, and hitting F5 does nothing.

2) Build And Run shortcut not customizable

I think this was a new command added in recent versions? In any case, it does not show up in the commands list in the keyboard customization window.

Also I've noticed in some places the commands are referred to as "Build" and in others (e.g. assembler toolbar tooltop_ as "Assemble". Is there any difference, or reasons why the naming isn't consistent?

3) Menus don't capture keyboard input

To reproduce:

a) Click anywhere in the code window
b) Press ALT+F
c) Attempt to use the arrow keys to navigate through the menus and press enter to select one. You'll see that instead, your keyboard strokes go into the code window.

To see how it SHOULD work:

d) Ensure the IO toolbar is visible
e) Click the whitespace in the I/O View window
f) Repeat step c from above. If the focus is not in the text editor it works properly.

4) I've noticed several other GUI-related bugs in the product (e.g. some C keywords not highlighting, menu commands mysteriously becoming disabled for no good reason, window focus issues when hitting the Run button, etc) and will provide more details if I notice patterns that reproduce them. The tool seems to have promise as a nice, simple AVR development environment, but these GUI/IDE issues are taking all the hard work that went into it and making the product feel sort of half baked..

Hope the feedback helps!

-Richard

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Note these were tested in AVR Studio 4.17 build 666 on Windows 7 and a slightly older version (4.16 I think?) on Windows XP.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You need to email this to avr@atmel.com so it automatically raises a support ticket.

Just posting here does not mean that it will enter their Bugzilla (or whatever their defect tracking system is)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Done; thanks!

(The "bug reporting" sticky might be updated to state what you mentioned. It implies the developers troll this forum and is a bit ambiguous as to the preferred place to post bugs i.e. here, email, or both)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Just to close the loop.. Atmel repied very quickly:

Quote:
Hi,

Thank You for the valuable feedback. We replicated the issues and all are correct. We will get them rectified with the future release.

Best Regards,
Atmel Technical Support Team

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

And shortly thereafter I sent them another cosmetic bug report below.

I'm new to AVR Studio.. are most people just putting up with these sorts of things, or are they using Eclipse or another IDE instead? Does Eclipse work with on-chip debugging?

Just curious.

Comment blocks not highlighted correctly if they extend past the editor viewport

1) Create and save a new .asm file

2) Create a comment block with /* on one line and */ a few lines below.

3) In between, write several lines of comments. Press ENTER repeatedly until the original “/*” line scrolls out of view past the top of the window.

4) You’ll notice the green font goes away, and keyword highlighting is applied to the comment block. This is corrected when you scroll back up to the start of the block.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:

are most people just putting up with these sorts of things, or are they using Eclipse or another IDE instead?

Don't know about others but I use one of my favourite editors outside of Studio just for editing then build within Studio Or at the command line (I use a dev system that supports such a luddite practice!). But for debugging it has to be Studio and a JTAGICEmkII - but when debugging you don't really care about its very limited editor.

Cliff