GoogleCodeExporter
commented
9 years ago it may be possible to preserve tab ordering, i'll see what i can do
i'll play around with the autohiding panel, in my experiance, they are shown
briefly
before hiding, which isn't much of an issue
the templates with the -F option are for Arduino only, it is required as the
Arduino
bootloader does not support device ID
the templates prefixed with Arduino are done so because they are meant to use
the
bootloader, the programmer is set to STK500 because the bootloader protocol is
the
STK500's protocol
i'm not sure what you would like to see in regards to avrdude's interactive
mode,
would you like another button just for that?
i'll add the sorting for the device and part dropdowns
i can see how remembering the last used file type could be useful, i'll add
that later
when you say highlighting of found matches, if you use the find/replace window,
they
are highlighted pink, if you use the panel i've made, double clicking a result
will
select it as blue. i'm not sure what you would like to see changed
i did not write the find and replace dialog, it came with ScintillaNet. What's
wrong
with "replace previous"?
the xml file for the attiny45 has an error, it lists the packages available as
[PDIP:SOIC:MLF], but the next xml tag is DIP. my code follows atmel's
convention and
looks for PDIP, SOIC, and MLF tags, but they do not exist. I can add a check for
non-matching tags.
burning of fuses is implemented by the fuse box in the configuration window
the idea is that you go to the fuse calculator website, calculate the fuses
that you
want to use, copy and paste in the arguments provided by the website into the
"fuse
box", and then burn them once, if something is wrong such as verification error,
tweak the fuses until they burn successfully every time and save them as such.
i'm not sure how you would like to constrain the flash memory for bootloaders
anything more that involves interacting with hardware and avrdude i'd like to
not
focus on. the editor is meant for the type of development that goes like: code
->
compile -> burn -> observe behaviour -> repeat .
for one-time actions such as loading a bootloader, it's not that much of an
annoyance
to somebody to just write the lock bits from the command line manually, you
only have
to do it once. if you are developing a bootloader, just keep it unlocked during
development
for anything more that involves avrdude, i'd sugguest you look into other tools
and
GUIs for avrdude. especially for eeprom images, as some people may keep multiple
images for different configurations and such.Original comment by frank.zhao.main@gmail.com on 18 Oct 2009 at 6:14
- Changed state: Accepted
Original issue reported on code.google.com by
bflaglie@c2i.neton 17 Oct 2009 at 7:33