Menu
▾
▴
usbpicprog-technical
|
From: Francesco M. <f18...@ya...> - 2008-11-29 20:11:21
|
Hi Frans,
I'm almost ready to implement all thread&XML stuff, as I've now a
sufficient understanding of upp_wx global architecture.
The last point to fix in the upp_wx_thread branch to bring it to the level of
the trunk is the selection of the hw that you want upp_wx connects to.
As I already said previously, I'd suggest adding an "Actions->Select programmer"
option which displays more info about _all_ the attached hardware (e.g. think to
2 upp programmers attached to the same computer) and lets you choose the
usbpicprog/bootloader you want.
I'd put there
- a "Current status: connected to XX on port YY" label
- a wxListBox which shows the programmers/bootloaders detected, their firmware
versions and the USB ports to which they are attached.
- "Connect", "Disconnect", "Close" buttons
sounds good?
Do you think the Hardware class would need big modifications?
Thanks,
Francesco
--
|
|
From: Frans S. <fra...@gm...> - 2008-11-30 11:22:27
|
2008/11/29 Francesco Montorsi <f18...@ya...> > Hi Frans, > I'm almost ready to implement all thread&XML stuff, as I've now a > sufficient understanding of upp_wx global architecture. > > The last point to fix in the upp_wx_thread branch to bring it to the level > of > the trunk is the selection of the hw that you want upp_wx connects to. > > As I already said previously, I'd suggest adding an "Actions->Select > programmer" > option which displays more info about _all_ the attached hardware (e.g. > think to > 2 upp programmers attached to the same computer) and lets you choose the > usbpicprog/bootloader you want. > > I'd put there > - a "Current status: connected to XX on port YY" label > - a wxListBox which shows the programmers/bootloaders detected, their > firmware > versions and the USB ports to which they are attached. > - "Connect", "Disconnect", "Close" buttons > > sounds good? Yes, it sounds good. Let's do so > > > Do you think the Hardware class would need big modifications? > I don't think so, well - maybe if there are more than one usbpicprogs connected, but that one is small. Today I don't have the ability to look at it, I'll check it later Thanks for the good work! > > > > > > > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Usbpicprog-technical mailing list > Usb...@li... > https://lists.sourceforge.net/lists/listinfo/usbpicprog-technical > |
|
From: Frans S. <fra...@gm...> - 2008-12-02 08:07:32
|
Hi Francesco, > > I'd put there > - a "Current status: connected to XX on port YY" label > - a wxListBox which shows the programmers/bootloaders detected, their firmware > versions and the USB ports to which they are attached. > - "Connect", "Disconnect", "Close" buttons > > I think we can just create one connect button / menu item (and of course a disconnect) After all I don't think it makes sense to be able to have multiple programmers connected at the same time. I think it's a good idea that you made the wxLogMessages "usbpicprog connected" etc, but don't you think they need a checkbox like "don't show this message again"? I don't know if there is a dialog in wxWidgets which has it by default, or if the wxLogMessage has a function like that. We can also make an option for it in the preferences dialog. Cheers, Frans |
|
From: Francesco M. <f18...@ya...> - 2008-12-02 19:18:09
|
Hi, Frans Schreuder ha scritto: > Hi Francesco, >> I'd put there >> - a "Current status: connected to XX on port YY" label >> - a wxListBox which shows the programmers/bootloaders detected, their firmware >> versions and the USB ports to which they are attached. >> - "Connect", "Disconnect", "Close" buttons >> >> > I think we can just create one connect button / menu item (and of course > a disconnect) > After all I don't think it makes sense to be able to have multiple > programmers connected at the same time. Well, in fact I proposed making a dialog for connection/disconnection mainly to be able to show some additional info about the attached hw: firmware version, USB port, etc. In future maybe it could be expanded to show realtime monitoring data, e.g. the voltage of the pump (this could be done easily using a PIC pin as A/D, isn't it?), etc... However you're right that probably two simple menu items which do a wxLogMessage with some info (e.g. "Usbpicprog v.xx connect on port yy") could be enough for now... > I think it's a good idea that you made the wxLogMessages "usbpicprog > connected" etc, but don't you think they need a checkbox like "don't > show this message again"? indeed, it would be very useful. > I don't know if there is a dialog in wxWidgets which has it by default, > or if the wxLogMessage has a function like that. > We can also make an option for it in the preferences dialog. I think I've made in the past a small utility for both loading/saving into a wxConfig such messages; it also included a wxLog modification IIRC... I'll search it in my past projects. Francesco -- |
|
From: Francesco M. <f18...@ya...> - 2008-12-03 23:29:57
|
Hi, Francesco Montorsi ha scritto: > However you're right that probably two simple menu items which do a wxLogMessage > with some info (e.g. "Usbpicprog v.xx connect on port yy") could be enough for > now... I've implemented this in the upp_wx_thread branch. I think it's now mostly ready to be copied in the trunk. One last thing I'd like fix is that when I choose the Actions->Autodetect menu item, even if the programmer is connected to the USB but disconnected from any external circuits, upp_wx happily says: "Detected: P18F2550" I think this is misleading. I'd prefer it to say: "No PIC detected!" I'm not really sure what Hardware::autoDetect does (I've added some error checking but the result doesn't change) but it looks to me like if it "detects" P18F2550 because that's the PIC used in the UPP programmer itself. I think that when the user chooses Actions->Autodetect, he doesn't want to know about the PIC used for the UPP programmer itself... Francesco -- |
|
From: Frans S. <fra...@gm...> - 2008-12-05 08:08:19
|
Hi, Francesco wrote: > Francesco Montorsi ha scritto: > >> However you're right that probably two simple menu items which do a wxLogMessage >> with some info (e.g. "Usbpicprog v.xx connect on port yy") could be enough for >> now... >> > I've implemented this in the upp_wx_thread branch. > > I think it's now mostly ready to be copied in the trunk. > Yes I think so too! I haven't changed much in the trunk version, so we can simply overwrite everything! In the mean time I have concentrated somewhat on the language files I got from some people, but as you have seen, they are in the branched version too. > One last thing I'd like fix is that when I choose the Actions->Autodetect menu > item, even if the programmer is connected to the USB but disconnected from any > external circuits, upp_wx happily says: > > "Detected: P18F2550" > > I think this is misleading. I'd prefer it to say: > > "No PIC detected!" > This is indeed a thing that I also wanted to change. What autodetect should do is reading the device id from the PIC. But when pictype can't find the detected devId, it will replace it with the "default pic" which is P18F2550. > I'm not really sure what Hardware::autoDetect does (I've added some error > checking but the result doesn't change) but it looks to me like if it "detects" > P18F2550 because that's the PIC used in the UPP programmer itself. > > I think that when the user chooses Actions->Autodetect, he doesn't want to know > about the PIC used for the UPP programmer itself... > sure, you are right Frans |
|
From: Francesco M. <f18...@ya...> - 2008-12-07 13:00:55
|
Hi, Frans Schreuder ha scritto: >> I think it's now mostly ready to be copied in the trunk. >> > Yes I think so too! I haven't changed much in the trunk version, so we > can simply overwrite everything! ok - then I've merged the branch back into trunk now. > In the mean time I have concentrated somewhat on the language files I > got from some people, but as you have seen, they are in the branched > version too. indeed; I got some conflict about them when merging and I hope I've solved them correctly; just to be sure you may want to check if the language files in trunk are the expected ones. Bye, Francesco -- |
|
From: Frans S. <fra...@gm...> - 2008-12-05 13:54:34
|
Hi Francesco, The current branch is now compiling well in wxWidgets 2.9.0, but this is not a released version of wxWidgets. For the time being, don't you think it is better to make the project compatible with at least 2.8.9? (I mean the wxQueueevent things) Frans |
|
From: Francesco M. <f18...@ya...> - 2008-12-05 20:28:00
|
Frans Schreuder ha scritto: > Hi Francesco, > > The current branch is now compiling well in wxWidgets 2.9.0, but this is > not a released version of wxWidgets. For the time being, don't you think > it is better to make the project compatible with at least 2.8.9? > (I mean the wxQueueevent things) Well, yes :) It's very difficult to ensure binary compatibility in linux so that providing a source release which builds against a released version of wx is indeed important. I didn't consider that before... I'll add some #if wxCHECK_VERSION() around to make it compile with wx2.8 but I still suggest building the released binary against wx29 (I'm trying to understand why the mouse wheel doesn't work in wxGrid under wxGTK... I hope to fix it soon in wxTRUNK). Francesco -- |
|
From: Frans S. <fra...@gm...> - 2008-12-05 21:13:23
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hi Francesco,<br>
<blockquote cite="mid:493...@ya..." type="cite">
<pre wrap="">Frans Schreuder ha scritto:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Francesco,
The current branch is now compiling well in wxWidgets 2.9.0, but this is
not a released version of wxWidgets. For the time being, don't you think
it is better to make the project compatible with at least 2.8.9?
(I mean the wxQueueevent things)
</pre>
</blockquote>
<pre wrap=""><!---->Well, yes :)
It's very difficult to ensure binary compatibility in linux so that providing a
source release which builds against a released version of wx is indeed
important. I didn't consider that before...
I'll add some #if wxCHECK_VERSION() around to make it compile with wx2.8 but I
still suggest building the released binary against wx29 (I'm trying to
understand why the mouse wheel doesn't work in wxGrid under wxGTK... I hope to
fix it soon in wxTRUNK).
</pre>
</blockquote>
Building against wx29 is no problem for the binary release, but I can
understand that people who want to build the source don't feel like
building the whole wxwidgets binary from svn.<br>
<blockquote cite="mid:493...@ya..." type="cite">
<pre wrap="">Francesco
</pre>
</blockquote>
</body>
</html>
|
|
From: Frans S. <fra...@gm...> - 2008-12-05 21:23:38
|
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<br>
<br>
Francesco Montorsi wrote:
<blockquote cite="mid:493...@ya..." type="cite">
<pre wrap="">Hi,
Francesco Montorsi ha scritto:
</pre>
<blockquote type="cite">
<pre wrap="">However you're right that probably two simple menu items which do a wxLogMessage
with some info (e.g. "Usbpicprog v.xx connect on port yy") could be enough for
now...
</pre>
</blockquote>
<pre wrap=""><!---->I've implemented this in the upp_wx_thread branch.
I think it's now mostly ready to be copied in the trunk.
One last thing I'd like fix is that when I choose the Actions->Autodetect menu
item, even if the programmer is connected to the USB but disconnected from any
external circuits, upp_wx happily says:
"Detected: P18F2550"
I think this is misleading. I'd prefer it to say:
"No PIC detected!"
</pre>
</blockquote>
I fixed it in r463<br>
<br>
</body>
</html>
|
|
From: Francesco M. <f18...@ya...> - 2008-12-05 22:09:44
|
Frans Schreuder ha scritto: > > > Francesco Montorsi wrote: >> Hi, >> >> Francesco Montorsi ha scritto: >> >>> However you're right that probably two simple menu items which do a wxLogMessage >>> with some info (e.g. "Usbpicprog v.xx connect on port yy") could be enough for >>> now... >>> >> I've implemented this in the upp_wx_thread branch. >> >> I think it's now mostly ready to be copied in the trunk. >> >> One last thing I'd like fix is that when I choose the Actions->Autodetect menu >> item, even if the programmer is connected to the USB but disconnected from any >> external circuits, upp_wx happily says: >> >> "Detected: P18F2550" >> >> I think this is misleading. I'd prefer it to say: >> >> "No PIC detected!" >> > I fixed it in r463 great! I'm looking at making the code wx28 compatible and to the "don't show me again" feature in log messages right now... Francesco -- |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X