This topic contains 43 replies, has 8 voices, and was last updated by 
AdamStrange
2 years ago.
-
Posts
-
@day – further to what aerobat said:
What (generally) are you doing when the official Ted crashes?
Editing, loading, cut, copy?
Ted21 is based on the original V1.02 codebase. This was the code that existed before Mark pulled Mojox into a modules and he rewrote the Ted2 code to make it more extensible. So I can’t help with any of the crashes you might be having ;(
I do know the original source very well, and it needed quite a lot of work to stop it crashing at the time. But it was usable and generally stable. My thoughts are that there is something nasty going on inside the new mojox and having it as a module has not helped this..
If there was Ted2Go only crash the reason would be code parser (completion stuff).
But there is a crash on original Ted2.
Anyway, we can fix it as soon as we can reproduce the crash.
if there is a crashes in the original ted2 then the fault is definitely in the mojox code then – As Said, Ted21 was based on the original mojox, but rewritten.
AH – wait a minute though
Ted2 was rewritten by mark with the new mojox stuff too. I agree that you need to have some more concrete bug reproduction system.
A suggestion here would be to create a log system with future ted2go. loggng major edits being done( cut, copy, paste, change document, etc) and constantly save this to disk before the action is carried out. When a crash occurs you will be able to see what was being done. Not a perfect solution, but it might be the best way forward for you?
Yes, maybe in the future…
@day Anything you miss, would like, want more of int Ted21?
its not a case of doing anything i can open up ted2go create a new file boom runtime error same happens even if i dont do ANYTHING just a blank window crashes the editor for me im starting to think there is a problem with memory and win 8.1pro 64bit.
i can keep devcpp or visio2015 going all day no problems hell i had my laptop on for a week while bug hunting in visio2015 and not one problem.
Blitzmax works fine also.
look il level with you i had a stroke few years back and i no longer am able to get what i wants to say out in words its why i wanted to convert my codebase to monkey (less to rewmember) but atm i am starting to miss the simplicity of Blitzmax/blitz3d mx2 is very cool But for me its starting to go into the realms of over complication.
im starting to strugle with how to join up my objects togeather. this is realy not a begginers language.
also mark in the editor for the love of god make it so you can see all members of a namespace as all you get is members of the file ur working on witch means have to keep swaping back and forth to find members that are not in that file but is a member of the namespace it makes it hard for idiots to stich objects togeather accros multi source files.
Adam in the editor is it posible to stop the window tab changeing to member view when you click on a src file as its annoying when you get the view changed when browsing code src files.
@day First off sorry to hear about your situation. I’ll try my best to sort things out on the Ted21 front for you.
OK. Just so i’m clear at this end.
Left panel (contains the file, view, debug and help) is called the browser.
I’m assuming you are viewing some help file of some sort, and when you select a source file the browser changes to View?
And you would like a switch to stop it doing this?
yes thats the correct panel and its when you single click a monkey2 source file in the file tab it auto changes to the member view tab so you have to reclick the file view every time.
its off putting when ur looking for stuff and it keeps changeing the tab.
ok, no problem. I’ll get it implemented for you and report when completed.
OK
I’ve updated Ted21 to prevent the browser from auto updating. basically I put in a switch for you.
https://adamstrange.itch.io/ted21
Let me know if it does anything odd. Both macOS and WiN version are upped
cool thats much better thx
I’ve yet to have the IDE crash, maybe I’m not trying hard enough
ok, so now we have it not crashing and everyone is happy. thoughts, suggestions. There are four new editors which will be integrated into it at some stage:
fontsprite editor
map editor
chip voice editor
chip tune editor
There is currently no documentation about all the new stuff either
Can I ask what version monkey you are using. I can then provide the updated files needed for compile/test – but not build
You must be logged in to reply to this topic.