![]() |
Forum Index : Microcontroller and PC projects : Micromite and Micromite Plus Beta 30
![]() ![]() |
|||||
Author | Message | ||||
Chris Roper Senior Member ![]() Joined: 19/05/2015 Location: South AfricaPosts: 280 |
I don't recall anyone asking for bulletproof, we are asking for flexibility. If you don't do something because someone else may break it then you will never do anything at all. WW has a valid need, I have a valid need that is slightly different, many others probably have a need but have not spoken up and no one knows what future use may be made of the functionality. In this case a Kid may break it, but all the kids learn something if he does and the teacher can then show them all how to fix it, turn it into a learning experience rather than disqualify the MicroMite. Cheers Chris EDIT: I take to long to Type, WW got in first, but I will leave my response as is. http://caroper.blogspot.com/ |
||||
CircuitGizmos![]() Guru ![]() Joined: 08/09/2011 Location: United StatesPosts: 1427 |
I don't have the source code (and the time to understand it) but I think what you are asking for would be solved with a hook to something (MM.HOOK residing in library space) just prior to the '>' prompt, and another hook when the editor opens. I don't know how difficult these hooks would be, but my guess is that the hook wouldn't be bad. Test to see if MM.HOOK (or whatever it needs to be) is present and call it. Again that probably wouldn't be difficult, but it might be that making sure that this apple doesn't upset the cart is the most work. I can see the benefit of having this hook and perhaps others. Micromites and Maximites! - Beginning Maximite |
||||
Geoffg![]() Guru ![]() Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
There seems to be a number of different requirements. Peter needs to run something at first powerup, WW at the prompt and others when the program starts. Due to the elegant design of the sub/fun functionality in MMBasic (shameless plug there ![]() MM.PROMPT If defined this will be run whenever MMBasic is about to display the command prompt (if this is defined the prompt (ie, "> ") will not be displayed). In this sub you can set colours, display your own custom prompt, setup I/O, etc. The only thing that would not work is CONST but you could use DIM. MM.EDIT This would be run immediately before the editor is run. In that you could set special colours. Remember that this is in addition to the features provided by MM.STARTUP and running the code in the library area before the main program runs. Other comments: Thanks, I will fix it. The options are listed in (what seems to me ![]() Chris, I could not reproduce it. It may be because your window dimensions in Tera Term do not match what the editor was expecting. OK, easy to do. That is strange and I cannot duplicate it. We will have to see if it repeats itself. Thanks, that is a silly bug ![]() Something like that might be feasible in the MX470 version but the MX170 version has completely use up all the flash, there is no more. Geoff Geoff Graham - http://geoffg.net |
||||
Geoffg![]() Guru ![]() Joined: 06/06/2011 Location: AustraliaPosts: 3292 |
Update: I just tried implementing MM.EDIT and it had unfortunate side effects. So it may have to be left out. Geoff Geoff Graham - http://geoffg.net |
||||
atmega8![]() Guru ![]() Joined: 19/11/2013 Location: GermanyPosts: 724 |
Hello, lots of interesting feature request here. I hope Geoff can focus on basic bugs. Fore me one of those bugs is the annoying fu**** win 10 USB Problem! As Microsoft reports, there are now nearly 100 000 000 ( Million) Win 10 installation in the world, i am only one of this. Imagine all the interested people out there who will plug in their MM + and getting no console. Lots of them will throw it away......, plugin their arduino's or other platforms and will never Comeback to MM+..... This cannot be good! Atmega8 |
||||
WhiteWizzard Guru ![]() Joined: 05/04/2013 Location: United KingdomPosts: 2944 |
![]() Is MM.PROMPT ok though? (assuming you've had time to implement this!) IDEA regarding CONSTs. Can you not go back to what you had before with and 'un-subroutined' lines of code being run at startup and hence have CONSTs defined here (as in your first implementation of Library); and then introduce MM.RUN to be a sub of code that runs at run-time ![]() Probably a thousand reasons that this won't work but just wanted to suggest it ![]() WW |
||||
![]() ![]() |
![]() |
![]() |
The Back Shed's forum code is written, and hosted, in Australia. | © JAQ Software 2025 |