Tools disappeared in Infragistics Toolbar

Posted by misiacik on Thu 11 of Jun, 2009 08:29 GMT

Hallo, everybody,

I have a problem with our tool...

After Infragistics upgrade to version 9.1 (prior version works well) - the control scan process is not able to find Tools from Infragistics Toolbars so I can not see them to translate.

Even old translation ml_UpdateControls items used to miss after Adding Alternative Runtime Support (we are using) so it demages old work!!!

Can you help, please?

Reads: 45480
Link
Posted by caco on Sun 14 of Jun, 2009 05:50 GMT

> Hallo, everybody,
>
> I have a problem with our tool...
>
> After Infragistics upgrade to version 9.1 (prior version works well) - the control scan process is not able to find Tools from Infragistics Toolbars so I can not see them to translate.
>
> Even old translation ml_UpdateControls items used to miss after Adding Alternative Runtime Support (we are using) so it demages old work!!!
>

Same problem here! If I'm not mistaken, it worked with 9.1 on the release version, but since the upgrade for HOTFIX 1 (build 2023) it stopped working. I upgraded multilanguage addin to latest version and still no good.

Tried rescanning the project by sources and designer and still nothing.

Does somebody knows a way out of this? Any update of the add-in that fixes it??

Thanks!!

Link

Posted by Phil on Mon 15 of Jun, 2009 20:16 GMT Germany

I can't reproduce this error at present.

I am using the current trial version, which is version 20091.1000. I cannot download the hotfix version 20091.2023, because it requires a subscription.

Misiacik, are you also using the hotfix version 20091.2023?

I don't see how I can fix this problem, until the hotfix is integrated into a version, which I can download as a trial version (probably 2009 volume 2).

Phil

Link
Posted by Phil on Tue 16 of Jun, 2009 22:22 GMT Germany

Hi,

I have just uploaded a new version (4.60.0031) which might fix the problem. Using the BasicFeatures sample program the Add-In now detects the tool objects and typically shows the SharedProps.Caption property, as shown here.
Image
As far as I can tell, the change is that the SharedProps property now has the attribute DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden), which causes the Add-In to ignore it.

(If the Add-In scans the properties of all child objects, it quickly gets into an endless loop. To prevent this, it only scans objects with SerializationVisibility = DesignerSerializationVisibility.Content, with one or two exceptions.)

Phil

Link
Posted by caco on Wed 17 of Jun, 2009 06:51 GMT

> Hi,
>
> I have just uploaded a new version (4.60.0031) which might fix the problem. Using the BasicFeatures sample program the Add-In now detects the tool objects and typically shows the SharedProps.Caption property, as shown here.
> Image
> As far as I can tell, the change is that the SharedProps property now has the attribute DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden), which causes the Add-In to ignore it.
>
> (If the Add-In scans the properties of all child objects, it quickly gets into an endless loop. To prevent this, it only scans objects with SerializationVisibility = DesignerSerializationVisibility.Content, with one or two exceptions.)
>
> Phil

Hi Phil,

Well, it did find Toolbar properties now, but only InstanceProps and not the SharedProps, which are those that are commonly in use. Could you check this out please? All our translations are for SharedProps, but more important is that all designers for Infragistics will add caption on SharedProps first and only if it's a override of something, then on InstanceProps...

Thanks in advance,
caco

Link
Posted by Phil on Wed 17 of Jun, 2009 20:22 GMT Germany

Hi Caco

can you make an example project and email it to me?

The change that I made should only affect SharedProps, so I can't understand why it would suddenly start to detect InstanceProps.

I'm not an expert on using the Infragistics controls and usually just test with the sample projects.

Phil

Link
Posted by caco on Thu 18 of Jun, 2009 08:57 GMT

> Hi Caco
>
> can you make an example project and email it to me?
>
> The change that I made should only affect SharedProps, so I can't understand why it would suddenly start to detect InstanceProps.
>
> I'm not an expert on using the Infragistics controls and usually just test with the sample projects.
>
> Phil

Hi Phil,

My bad. I tried to install *.0031 over 0029 and it didn't really worked. Just today I double checked the about form on the AddIn and saw that I was still using 0029. I uninstalled and reinstalled 0031 and now everything seems to be ok. Just ran a rescan on a big project and everything is there... Thanks!!

Link
Posted by caco on Sun 21 of Jun, 2009 06:15 GMT

> Hi,
>
> I have just uploaded a new version (4.60.0031) which might fix the problem. Using the BasicFeatures sample program the Add-In now detects the tool objects and typically shows the SharedProps.Caption property, as shown here.
> As far as I can tell, the change is that the SharedProps property now has the attribute DesignerSerializationVisibility(DesignerSerializationVisibility.Hidden), which causes the Add-In to ignore it.
>
> (If the Add-In scans the properties of all child objects, it quickly gets into an endless loop. To prevent this, it only scans objects with SerializationVisibility = DesignerSerializationVisibility.Content, with one or two exceptions.)
>
> Phil

Hi Phil,

I'm having the same problem we had wth the toolbars with the UltraGrid component (Infragistics). It doesn't scan columns captions. I would guess it's the exact same thing.

Could you check this out and release a fix? Is this something we could configure on a configuration file somewhere, so those exceptions could be made by us users?

I guess that Infragistics probably has a lot of other controls doing the same. Maybe you should scan for all Infragistics products the way you do now with the tree? Maybe a project property to "deep scan Infragistics components"??

Thanks and regards,
caco

Link
Posted by Phil on Sun 21 of Jun, 2009 20:41 GMT Germany

This is basically the same problem, in this case for the UltraGridLayout.Bands property, which now has SerializationVisibility = Hidden. Hard coding a check for the Bands property seems to work, but that is not a real solution.

I have also noticed that both ToolBase.SharedProperties and UltraGridLayout.Bands have the attribute LocalizedCategory("LC_Data"). This is an Infragistics attribute and I can only guess at the significance.

However, I should be able to detect this attribute and will try to use it as a criterion for scanning into this property. If it works, that would be better than hard coding numerous specific properties.

As I already mentioned, the problem with any kind of deep scan is that it can easily become recursive. All you need it a child object with a property which returns its parent, and you have an endless loop.

I am still working on this problem, but I hope to upload a fix in the next day or two.

Phil

Link
Posted by caco on Mon 22 of Jun, 2009 05:55 GMT

> This is basically the same problem, in this case for the UltraGridLayout.Bands property, which now has SerializationVisibility = Hidden. Hard coding a check for the Bands property seems to work, but that is not a real solution.
>
> I have also noticed that both ToolBase.SharedProperties and UltraGridLayout.Bands have the attribute LocalizedCategory("LC_Data"). This is an Infragistics attribute and I can only guess at the significance.
>
> However, I should be able to detect this attribute and will try to use it as a criterion for scanning into this property. If it works, that would be better than hard coding numerous specific properties.
>
> As I already mentioned, the problem with any kind of deep scan is that it can easily become recursive. All you need it a child object with a property which returns its parent, and you have an endless loop.
>
> I am still working on this problem, but I hope to upload a fix in the next day or two.
>
> Phil

Many thanks! I agree with you on the recursivity, and I know for sure Infragistics does have parents that point to children that point to parents..

Anyway, I guess that the LC_DATA attribute you found looks like a good lead. I'll try to find something about it, and maybe this will be a great solution for all Infragistics translations.

In the mean time, I'll be looking forward for the new release.

Thanks again and regards,
caco

Link
Posted by Phil on Mon 22 of Jun, 2009 20:16 GMT Germany

Can you try out the newest version (4.60.0032)?

I hope that this one shows the column headers.

Phil

Link
Posted by caco on Tue 23 of Jun, 2009 05:18 GMT

Just tried 0032 build. It does find all column names and other strings that could have been set, but it stopped finding Shared Properties for tools in the Toolbar (finds only Instance props). Is it possible? Did you rolled back the changes done in 0031?

I tried using the new parameter setting for putting nested controls on top ON and OFF, with same results.

I guess a combination of the technique used on 0031 with the one on 0032 will do?? ;)

Thanks again and regards,
caco

Link
Posted by Phil on Tue 23 of Jun, 2009 20:36 GMT Germany

My error, sorry. I have uploaded another fix (4.60.0033).

Phil

Link
Posted by caco on Wed 24 of Jun, 2009 05:15 GMT

> My error, sorry. I have uploaded another fix (4.60.0033).
>
> Phil

Hi Phil,

Just running .0033 now. I'm not sure if it's going to find everything, but one thing for sure, it's taking FOREVER. A relatively big project that would take 5 minutes to scan (controls via designer + source) is already on minute 6 and it's not even in the first third of the project. It looks like it gets stuck on Infragistics controls (at least on the UI it's what's showing when it stucks). It's working on full throttle and still. At first, I just restarted VS because I thought it's frozen, but now I'm letting it work and it's progressing, really slow but it is.

Another strange issue I have is that when opening some projects and not rescanning (or opening from previous scan) I get a "Invalid parameter" on the output window, not exception from add-in but then add-in opens without the panel where one can choose between control and source code. The rest works... (This seems to be something not new to .003x versions though).

Thanks and regards,
caco

Link
Posted by caco on Wed 24 of Jun, 2009 05:25 GMT

Well, right now 17 minutes have passed and still on 40ish % mark. It's stuck on a ultraPrintPreviewDialog control. Looking back, it's stuck on that same control (different form) previously when I restarted VS.. I guess something regarding recursive calls on scan??

I'll post the results of the scan as soon as I get them though.

Thanks and regards,
caco

Link
Posted by caco on Wed 24 of Jun, 2009 07:34 GMT

Hi Phil,

After almost two and a half hours it finished!! It did work, but it seems that it brings all the Appearance objects into list, and those have only the FontData.Name property (which I don't think it's something someone would like to translate. ??).

Anyway, not really a solution. Maybe ignoring Appearance objects would improve it??

Another issue is that Tools appear as stand-alone and under the Toolbar with both Shared and Instance properties. It's not really a problem but can be if someone chooses different text for each. (I'm I right here??)

Thanks again for the efforts and regards,
caco

Link
Posted by Phil on Wed 24 of Jun, 2009 22:12 GMT Germany

Version 4.60.0033 scanned into any property with the LocalizedCategory attribute, with any value.

I have uploaded a new version (4.60.0034) which scans into properties with LocalizedCategory=Data, but not if the attribute has other values. Possible values appear to be Appearance and Behavior.

I hope that this version is more useful. Obviously scanning for 2 1/2 hours is useless.

Sorry about these difficulties, but not really very familiar with the Infragistics controls. I have never personally used them on a project.

Phil

Link
Posted by caco on Thu 25 of Jun, 2009 05:13 GMT

Hello Phil,

Just ran .0034 and everything is back to being great! Fast scan time, all Tools, grid columns and such are back.

Thanks you very much for the prompt replies and effort you put into the add-in! A real time saver!!

Regards,
caco

Link
Posted by misiacik on Tue 23 of Jun, 2009 14:23 GMT

Uuuuups!
Something bad had happened from *.031 - *.032!
Tools has disappeared again...

Link

Posted by misiacik on Wed 17 of Jun, 2009 09:23 GMT

Hallo,
I am not sure, but after last update *.0031 Building process in Visual studio 2008 falls if there is Add-in started in. Am I true, or there is something wrong in my computer environment?

Link
Posted by Phil on Wed 17 of Jun, 2009 20:33 GMT Germany

It could be related to the Add-In.

I have a dirty flag logic for the resource files. When you start a build, the Add-In checks whether there is anything to write to the resource files and asks you whether you want to update them immediately.

You can avoid this by updating them yourself, before starting the build.

I have always had some problems with this logic and will probably remove it in the next (major) version. I am currently working on a new version, in which all changes to the resource files will be made immediately. It is much to easy to forget this step, and it is not obvious for new users.

Of course, your build problems might have nothing to do with this.

Phil

Link