All Answers

0 votes
In reply to: Focus Problems

Ok, I found something that I can reproduce.  Maybe it’s related (I.e. fixing it will fix the other problems too).

  • run my test program with Firefox 52.0.2 (without or without commenting out mainform.toolbar.Focus())
  • hit ctrl-P
  • it should display “ctrl-P” in an AlertBox
  • click on the browser background
  • hit ctrl-P
  • it displays a print dialog
  • click anywhere in the form
  • hit ctrl-P
  • it still displays a print dialog
  • drag the form around
  • hit ctrl-P
  • it still displays a print dialog

I believe that clicking on the form, or dragging it, should set focus to the form, and the Accelerator handler should handle ctrl-P.  Correct?

I wonder if some variation of occurs, sometimes, at program startup – somehow the browser background gets focus, and then the form can never get focus.

  • David answered Apr 17, 2017 - 6:21 pm
0 votes
In reply to: Focus Problems

Aaarghhh…  There is definitely a race condition, or something 🙂

I tested problems 1 and 3 with Firefox 52.0.2 and consistently got the print dialog instead of my ctrl-P handler.  So, I installed some screen cast software and tried to get a screencast of the error.  Then, it worked correctly every time.  I thought maybe the screencast software was making the computer run slowly, and somehow that was helping, so I exited the screencast software, and it began to fail again.  Then, I tried to capture it with my phone, and it started working correctly again.  It’s like it knows when I want it to fail 🙂  Now, it works consistently.  I can’t make it fail.

I don’t know what conditions are necessary to reproduce these errors, but they definitely occur.  I just wish I could prove it.

My guess would be that sometimes the code that sets focus to the main form runs before the form fully exists, so the form doesn’t get focus.  But, of course, that’s just a guess.

I’ll keep trying…

  • David answered Apr 17, 2017 - 5:55 pm
0 votes

Same as https://wisej.com/support/question/hi-something-like-particle-js

As I wrote, you can import and use anything without an extension. The Wisej extension controls wire .NET properties and methods to the widget and make integrate it a bit more deeply. The different types of integration are described here: https://wisej.com/?smd_process_download=1&download_id=3921

  • Luca answered Apr 17, 2017 - 4:32 pm
0 votes

I don’t know which widget it is. With Wisej you can use any third library as you’d do (actually easier) with any other web environment.

Also see: https://wisej.com/support/question/hi-something-like-particle-js

  • Luca answered Apr 17, 2017 - 4:30 pm
0 votes

Hi Andrew,

thanks for your feedback. Based on your questions we researched some more and found a way to add external plugins
to our CKEditor extension. It has been updated, so please download it again from our extension section.

Now you can add as many plugins as you like.

We tested with a youtube plugin that can be downloaded here: http://ckeditor.com/addon/youtube

Put it into your project under /ckeditor/plugins

Then you can set it up in the External plugins collection property as following:

Then you can add it to the Options property like this:

This way you already see the changed layout of CKEditor in the designer !
If you want to change it at runtime, please keep in mind to call ckEditor1.Update()

Hope that helps.

If you encounter any problems in integrating your custom plugins, please forward them to us and we´ll take a look.

Best regards
Frank

0 votes
In reply to: Focus Problems

Thank you for the test case. This is what I found:

  1. I can only reproduce on IE, in fact on IE calling preventDefault() doesn’t stop certain system keys.
  2. Good catch! We didn’t consider that some widgets that may be the source of keyboard events if if not visually focused are not Controls on the server side, but are components. Wisej uses “lightweight” components instead of controls for toolbar buttons, tools in editors, status bar panels, etc. The common interface is IWisejComponent. We’ll have to changed the event args. Logged as WJ-8195.
  3. Cannot reproduce. The first window becomes active automatically, you can check using Form.ActiveForm == mainform. The active form automatically focuses the first control in the tabbing order. I tried your sample as-is and added a text box, and removed all controls, it always seems to work in Chrome and IE. But if you click outside of the form, the form loses the focus to the browser but it remains active. Maybe we can improve the accelerator processing to route the accelerator key to the active form also when the keydown is coming from the document element.

See screen cast of the test using your sample:

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

 

  • Luca answered Apr 14, 2017 - 8:43 pm
0 votes

Thanks! Found the issue with the DOM. Logged as WJ-8194. Should be fixed in the upcoming update.

  • Luca answered Apr 14, 2017 - 5:29 pm
0 votes

F11 and Esc.

You can detect in Wisej whether the browser is in full screen reading Application.Browser.IsFullScreen.

You can detected whether the browser supports full screen reading Application.Browser.Features.fullScreen.

You cannot switch to full screen programmatically, browsers block any attempt to go full screen that is not initiated by a user click (no ajax or delayed calls). If you add a button on a page, you must handle the click on the client side and use: window.fullScreenApi.requestFullScreen(). Wisej adds the full screen api to windows.

 

 

  • Luca answered Apr 14, 2017 - 4:56 pm
0 votes
In reply to: FCK Editor

We have just released CKEditor extension and TinyMCE will follow shortly.

See extension page: https://wisej.com/extensions/

Best regards
Frank

0 votes

Hi Andrew,

we have released our CKEditor extension now.

It´s available here: https://wisej.com/extensions/

Best regards
Frank

0 votes

Hi Luca,

Yes, most of time now, text is selected when entering edit mode.

 

Pierre

0 votes

Everything seems fine now. 🙂

0 votes

Yes, we have pulled .53 and are uploading .55. Sorry about the regression.

  • Luca answered Apr 12, 2017 - 3:06 pm
  • last active Apr 12, 2017 - 3:35 pm
0 votes

Yep, .53 released this morning has been replaced by .55 due to this regression that unfortunately we didn’t catch in time.

  • Luca answered Apr 12, 2017 - 3:29 pm
  • last active Apr 12, 2017 - 3:34 pm
1 vote

Yes, “cookieless”: true in the json config file. A new tab will get a new session id in the url.

  • Luca answered Apr 12, 2017 - 3:22 pm
0 votes
In reply to: IFramePanel refresh

Hi Matthew,

Wisej.Web.IFramePanel.Reload() has been added in the latest Wisej release (1.3.53).

Best regards
Frank

0 votes

Hi Cris,

a new build (1.3.53) has just been uploaded that includes the fix that Luca mentioned (for WJ-8187)

Best regards
Frank

0 votes

Hi Robin,

please try again with our latest build (1.3.53).

Best regards
Frank

1 vote
In reply to: UserPopup Resize Issue

Hi Adil,

a new build has just been uploaded (1.3.53).

It fixes both of your issues, logged as WJ-8189 and WJ-8190.

Best regards
Frank

Showing 9221 - 9240 of 11k results