All Answers

Hi, Frank,

I’ve done a complete uninstall-reinstall-PC restart cycle.

I also checked all drives for any WiseJ references/files – none found after uninstall.

Are there files stored in hidden folders?

All 3 VS versions were checked when installing.

Still cannot see the WiseJ2 templates in new projects in VS2017, VS2019.

In VS2015, the option shows, but there are no templates (blank panel). VS2015 also shows a WiseJ(presumably) V1 option, and a project is created, but the form cannot be designed.

So, your help to manually install templates will be appreciated. Or a different approach if you think it will be faster.

I’m also happy to do a cleanup of any files that may have gotten “lost” – just let me know where to look.

I will add that my PC had a disk failure late 2019, and that the recovered backup version was quite old. It hasn’t caused any problems with other applications, but some settings and user configurations were affected – its possible this is causing the issue with WiseJ.

I also have VWG 10 installed on this PC – will that cause an issue?

Regards,

Geoff

Hi Geoff,

this usually happens if there is a mix of Wisej 1.x and Wisej 2.x code.
Wisej 1.x reference Wisej.core.dll and Wisej.web.dll while Wisej 2.x only references Wisej.framework.dll

Please also note that when running Wisej 1.x and Wisej 2.x on the same machine,
there are 2 groups in the Visual Studio Toolbox.

If you accidentally drop a control from the Wisej group instead of the Wisej 2 group onto a Wisej 2 window
the error you described can occur too.

Hope that helps.

Best regards
Frank

Hi Geoff,

this can probably be fixed by reinstalling Wisej and checking all 3 Visual Studio versions (2015,2017 and 2019).

If this does not help, I can send you a link to the project templates and how to reenable them for 2017.

Best regards
Frank

I was finally able to achieve what I was looking for from your sample (resize to a limited width and height while preserving the aspect ratio, and without risking a skew of the image)

in wisej.web.ext.ImageUpload.js I modified the img.onload function like this

 img.onload = function () {

 //set max width and height we are willing to accept
 var maxWidth = imageSize.width;//800;
 var maxHeight = imageSize.height;// 600;

 //get the original source photo width and height
 var srcWidth = img.width;
 var srcHeight = img.height;

 //define our target size variables
 var newWidth = srcWidth;
 var newHeight = srcHeight;

 //only need to resize if source dimensions exceed our maximum dimensions
 if ((srcWidth > maxWidth) || (srcHeight > maxHeight)) {
 //Conserve aspect ratio of the original 
 var ratio = Math.min(maxWidth / srcWidth, maxHeight / srcHeight);

 //set new dimensions with aspect ratio preserved
 newWidth = srcWidth * ratio;
 newHeight = srcHeight * ratio;
 }

 canvas.width = newWidth;
 canvas.height = newHeight;

 ctx.drawImage(img, 0, 0, newWidth, newHeight);
....

(the rest is identical)

in the bottom, below  document.body.appendChild(img); , I commented out the setting of img.width = imageSize.width and img.height = imageSize.height.  Essentially this changes the behavior so the input values specify a MAXIMUM width and height, instead of a fixed width and height.

Next step is trying to implement in an existing project.

Would you be interested in adding these changes and including the ImageUpload class in a future WiseJ?

regards,

Andrew

nobody from support can check this problem with an Iphone?

Hi HSoft,

Can you translate the error message to english or perhaps provide a small sample?

Best regards,

Levie

Can you send a sample app and a description of the issues and which which theme?

That’s only for the embedded adobe viewer. Browsers stopped using it years ago. Chrome uses it’s own viewer. Firefox uses pdfjs, Edge uses its own.

In case, you set the custom url when you set the viewer type to Custom.

Have you any mobile theme or plan for future?, app use very difficult on mobile with clasics themes

Thanks

Hi Christian,

I tried. See performance log below. In Chrome hit F12 and enable Verbose logging (running in debug mode) and you will see all the internal logs in the console.

What this shows is that the payload for the initial creation of 801 controls (window + 800 children, of which now 400 are comboboxes…) was 554KB (compressed 11K, to see this you have to look at the websocket messsages in the network tab). To render the 801 controls it took the javascript code 1.3 seconds. When creating 400 PictureBoxes instead (see below) the time elapsed drops to 658ms. That’s because of the additional button widget in the combobox. I tried with 400 TextBoxes and the time is 615ms.

Once the javascript is done building the DOM, the painting time is the browser’s job.

If you need to create 400 combo boxes I’d suggest to: a) if it’s a repetitive pattern use the DataRepeater, b) if not, do not populate the items list at first, populate it when dropped down the first time; c) if you have many items enable the VirtualScrolling property (we have a project with 93,000 items in ComboBoxes that crash windows on the desktop and they work perfectly, also with the filter AutoCompleteMode with VirtualScroll=true, when false it also crashes the browser).

HTH

400 ComboBox + 200 Labels + 200 Panels

009043 Wisej: Process Response length: 554851
009058 Wisej: Process Actions count: 1
009061 Wisej: Process Action 3
010391 Wisej: Action Create created: 801
010395 Wisej: Process Action 4
010395 Wisej: Action Update updated: 0
010395 Wisej: Process Actions elapsed: 1337 ms

400 PictureBox + 200 Labels + 200 Panels

003102 Wisej: Process Response length: 436051
003118 Wisej: Process Actions count: 1
003121 Wisej: Process Action 3
003775 Wisej: Action Create created: 801
003776 Wisej: Process Action 4
003776 Wisej: Action Update updated: 0
003776 Wisej: Process Actions elapsed: 658 ms

Hi Onur,

Have you seen the ColumnFilter extension?  This would be an easy way to add filtering functionality to your DataGridView.

Check this out: https://wisej.com/blog/columnfilter/

For a list of full extensions, check out our GitHub repository: https://github.com/iceteagroup/wisej-extensions

You can find a demo of the ColumnFilter extension here: https://github.com/iceteagroup/wisej-examples

Alternatively, if you don’t like the ColumnFilter extension you can add a new row at index 0 in your DataGridView and add an event handler for CellValueChanged and EditingControlShowing to show an appropriate filtering control (i.e., ComboBox, TextBox, etc.) and handle the filtering yourself.

Let me know if this helps!

Best regards,

Levie

Hi Luca,

try replace the two picturebox with two combobox. The time increases significantly, even if they are empty. If you put some items the time increases considerably

bye

Cristian Zerbinati

Hi Ulisses,

issue #2125 is fixed in Wisej dev build 2.1.37.

Best regards
Frank

Hi Angelo,

it´s fixed in Wisej dev build 2.1.37.

Best regards
Frank

Hi Luca

See attached example.

Whilst the JavaScript is set to true in the designer nothing happens on the client side

Change it to false in the designer and it starts working.

Actually I just noticed that while your test says 200 it is actually creating 800 controls: 200 panels + 400 picture boxes + 200 labels. The browser side timing shows 793ms (rendering frame). If I run the test with 200 controls I get less the 300ms on the browser and a total round trip of about 450ms. Which is on average the speed I observed on other projects:

800 controls: 800ms browser rendering, about 1.3 seconds (full round trip)

200 controls: 300ms browder rendering, about .5 seconds (round trip).

We can’t get any faster.

https://www.screencast.com/t/guu0nYx3Kld

My tests show 93ms to create the controls and 730ms to process them on the client. When you show a message using the appear event you are adding the communication lag, which is another few milliseconds. The total for me is 1.3 seconds including the network time. You can’t make it faster than this and I don’t see the kind of not smooth or slowness that you mention in large projects I’m working on.

My experience with VWG controls is that the creation is faster and the management is slower. In any case, this is the speed we have and there isn’t any room to increase it since it’s browser rendering speed.