Hello,
In the past I've written the INI++ Objects, the Chart Object (With CB) and the spell checker object, as well as other smaller objects. For a full list, consult my website.
As I haven't been following the forums for a while, what are the current known bugs or requested features on these objects?
Perhaps I can fix some problems.
Thank you,
- Jack
Chart object not working with build 253. Also if you can please add option to draw few functions at one screen.
Hey Jax! :)
I only remember this about the Spellcheck object. :D
I'd like to see an object that can adjust the contrast of the screen. I've seen one for brightness, but not for contrast.
So, ChrisBurrows, which object shall Jax add this to? ;)Quote:
Originally Posted by Jax
In chart object option save image to file work only with edittime but not in exe.
ChristBurrows, that doesn't really fit into any existing object, and so I won't do that. Sorry.
ColdFire: Those two problems have been noted. Hopefully I will get a chance to work on them. However, I am not sure what you mean by "[...] can please add option to draw few functions at one screen?"
Gustav, yes you are right I did want to add those features in. Really I should be able to extend it to arbitrary letters, so that it isn't restricted to just English and German, too.
Probably he meant that he would like to have 1 chart object to load few types of data from few sources and draw graphics for all of them (multiple charts in one object).
Welcome back :P
Personally I'm irritated with your foldering -> Data -slash- Runtime insted of Data\Runtime
:)
You can change the chart type at runtime (although this is an advanced feature), and you can also plot multiple lines on a scatter plot. You can also simulate multiple data sources in bar charts by changing the colours. So I don't think I need to make any changes there.
Thanks Fanotherpg :) Is that in the installer?
I need to show data in chart type XY. I can't show it on bar or pie. Look I need to draw blue and green line at one chart almost like here http://imageshack.us/photo/my-images/810/wykress.png/
Quote:
Originally Posted by Fanotherpg
No, it's in the ZIP downloads. Can't you just make a Runtime folder inside the Data folder so we can extract the zip directly to the MMF2 directory like with every other extension in existence?Quote:
Originally Posted by Jax
The following is from the advanced features section of the documentation:
Also I thought the Chart Object could only be distributed as an installer to stop the bad guys? I don't think any distribution without an installer is allowed. Certainly if you look at my site, it is an installer. So it has been done by somebody else (I assume unofficially, although CT may have done it I suppose).Quote:
Data-Sets
The Chart object in continuous made has a limitation – each series position can only have one value position associated with it. This is annoying because some graphs require two or more values associated with it. For instance, think of the graph of y2 = x. There are also some situations where you wish to display more than one line on the graph at the same time. This is solved in the Chart object by Data-Sets.
There are nine data-sets, indexed by the numbers 0 to 8. All the data-sets are shown on the graph at the same time. You can change this by the “Set data set” action in the ‘Values/Advanced’ sub-menu.
Each data-set has its own set of data-points and its own line and marker settings. Therefore actions such as ‘Set line colour’ or ‘Set Marker Thickness’ apply to the current data set. The same is true for expressions like ‘Get number of data points’.
The auto-range modes take into account data-points on all data-sets.
I haven't had any issues since you helped the last time around (thanks!), so INI++ seems pretty stable for now
A very complex bug with String Replacer.
http://community.clickteam.com/showthread.php?t=67599
Jax, I have been using INI++ for quite a long time now and it's rather stable. However, I was wondering would it be possible to create a 'Virtual INI' extension with hopefully not too much work utilising the exact same system you already have except reading/writing is to/from the memory rather than a file?
The reason I ask is sometimes it's an easier and more efficient alternative to using an array, I've know a few people that could benefit from this. Just curious.
Apart from that, INI++ stands up well!
Isn't that what INI++ does? I mean, its just writing into memory when you edit it- applying changes to the file only when you choose to (you can deactivate the autosave feature).
PT, I'm not sure, I just asked on a whim without investigating how it works. It could be using a temporary file for the INI?! I mean the ability to have it global throughout frames without writing a single file for example...?
It does not use a temporary file and it will never use any file if you disable autosave:
http://www.lb-stuff.com/MMF2/Ini++/ (Click "What's New?")
It even has a "Global Data?" tickbox as the first thing in its options! ;)
Indeed LB is correct (naturally it will save if you manually use the 'Save'/'Save as' actions though!).
I'm very glad to hear that INI++ is stable now. I was worried I may not have actually fixed the last problem correctly. If anybody has had problems with it though, please tell me!
I will look at the String Replacer bug
There is one thing that still bothers me Jax - I have two INI++ objects, one is "Ini++ 1.5" and the other is "Ini++ 1.5 Object" - which is more up to date?
If would be awesome if there wen't 4 versions of the Ini++ object/v1.5/1.6/etc. Is it possible to just keep them in only one object in future updates?
Jax the Ini++1.5 crashed when loading and saveing the encrypted file.
I'm installed the MMF2 Beta 1 after build 253.
MFA:
http://prester.org/mmf2/cgi/w2box/da...yption_test.7z
EDIT: This old version not crash.
http://community.clickteam.com/showthread.php?t=55733&p=445752&viewfull=1#post445 752
I have written the following in order to explain the 'multiple versions of Ini++' issue. The short answer is: there are only two versions, and there had to be two versions.
The long answer is:
Quote:
The situation is that there are versions of the Ini++ object. The original, and Ini++ v1.5. The latter was made when the Ini++ object behaviour changed. In particular, it no longer enforced items and groups to be in sorted order. Therefore I could not release this as an update to the original, as it could break peoples code. To make things worse, this was not something which could be an option either (without some rewriting of code in the original). It was called Ini++ v1.5 as a nod to Multimedia Fusion v1.5, which was Multimedia Fusion v1.0 plus many new features.
Naturally, there have been different releases of the ‘Ini++ Object’ and the ‘Ini++ v1.5′ objects, but both kept calling themselves that name. There is no ‘Ini++ v1.6′ object. There is no ’Ini++ v1.1′. Just the two mentioned. They have the file names ‘Ini++.mfx’ and ‘Ini++15.mfx’ respectively.
So why the confusion?
The problem stems from the fact that although the behaviour of Ini++ v1.5 changed from that of the original, it was still compatible with the original Ini++ object. That is, if you took ‘Ini++15.mfx’ and renamed it to ‘Ini++.mfx’, then any MMF application using the old version would suddenly be ‘upgraded’ to the new version. If you knew your program wasn’t going to stop working because of the changes, this was a great way to make use of the new features without copying over all the events to the new object. Quite a lot of people did this.
It was entirely deliberate that you could do this. In fact, Ini++ v1.5 has a few actions which have no menu items exactly for this purpose. For if they were removed from the code, then this renaming method might not work.
You would expect that if you did this you would see two identical looking objects in the ‘Create new object’ dialog. The same icon, the same text: ‘Ini++ v1.5 Object’. In fact, this is not what you see. Multimedia Fusion will rename the second object to ensure it doesn’t have the same name, so you actually end up with ‘Ini++ v1.5 Object’ and ‘Ini++ v1.5 Object 2′.
The first one (selected in the picture) actually has the file name ‘Ini++.mfx’ and the second has the file name ‘Ini++15.mfx’.
An earlier version of the Ini++ v1.5 Object called itself simply the ‘Ini++ v1.5′ object. Therefore if both ‘Ini++.mfx’ and ‘Ini++15.mfx’ were that version, you would in fact get ‘Ini++ v1.5′ and ‘Ini++ v1.6′ in the dialog, as it intelligently renames. Therefore any object calling itself ‘Ini++ v1.6′ is just an illusion. (Indeed, the title of the object was renamed after it was noticed this happened to avoid this confusion)
But perhaps you are seeing this anyway, despite not being one of the people who renamed ‘Ini++15.mfx’ to ‘Ini++.mfx’? Unfortunately, this is common. The first installer for the first release of Ini++ v1.5 actually installed the file as ‘Ini++.mfx’, which was obviously complicated the situation. (I didn’t make this installer. Later installers install it correctly.) I believe that the one of the extension updaters for MMF will also distribute Ini++ v1.5 with the filename ‘Ini++.mfx’. Combined, this means that nearly everybody will have this problem.
Perhaps I will solve this in future by having the next installer install the original version of Ini++ as well. Or perhaps by making sure it is uninstalled (as you shouldn’t really be using it anymore anyway – it exists only for compatibility reasons now).
So which version is the latest version? Well, it is quite possible they are both the same version. Make sure you are using the version with the file name ‘Ini++15.mfx’ (you can tell this by selecting the object and clicking the ‘About’ tab in the properties viewer). Ensure this is up to date by installing the latest release. If you don’t use ‘Ini++.mfx’, perhaps you should delete it.
I should have two versions of Ini++1.5?
I tried replaced the load action to new version. But, it still crash.
Did you confirmed the crash bug?
MFA link was dead. I've re-uploaded here.Quote:
Originally Posted by ASD
http://prester.org/mmf2/cgi/w2box/da...yption_test.7z
Yes, I get the crash. I'll attempt to look into all these problems when I get a chance.
No, try re-reading the post: You will probably have Ini++.mfx and Ini++15.mfx. If they both happen actually be the latest release of Ini++ v1.5 (renamed in the former case), then you will get the appearance of different versions.
Is there any chance to see if Ini++ could be made compatible with the iOS exporter?
That would be fantastic!
Hey Jax! Any news about the update of the Spellcheck object? ;)