Welcome, Guest
Username: Password: Remember me
Visual Objects

Please use this forum to post questions about Visual Objects and Vulcan.NET
  • Page:
  • 1

TOPIC:

Editing exported VO GUI in VS Designer leads to broken gui 07 Nov 2022 15:43 #24349

  • hilberg.it
  • hilberg.it's Avatar
  • Topic Author


  • Posts: 63
  • Hi,
    following issue: When I try to edit an exported VO GUI in XSharp/Visual Studio Designer, *.xsfrm and *.rc and *.prg files gets regenerated. So far so good, but the regeneration breaks the previous layout/sizing of controls. I believe it has something to do with screen resolution also. I have to resize all controls by hand to fix it.

    Did anyone else experience this behaviour?

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 07 Nov 2022 16:55 #24351

    • Chris
    • Chris's Avatar


  • Posts: 3736
  • Hi,

    Were the VO windows created and then exported and edited in X# in the same machine, or at least both had the same screen settings? If not, can you please post the specifications in both machines?
    XSharp Development Team
    chris(at)xsharp.eu

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 07 Nov 2022 17:42 #24353

    • hilberg.it
    • hilberg.it's Avatar
    • Topic Author


  • Posts: 63
  • Hi, with specs you mean resolution?

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 07 Nov 2022 17:51 #24354

    • Chris
    • Chris's Avatar


  • Posts: 3736
  • Yes, resolution and system font size.
    XSharp Development Team
    chris(at)xsharp.eu

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 07 Nov 2022 20:10 #24357

    • wriedmann
    • wriedmann's Avatar


  • Posts: 3242
  • Hello,
    this is/was also an issue in VO.
    If you have a window designed with normal sized fonts, and save it with large fonts, the positions get changed.
    Therefore I always used normal sized fonts when working with VO.
    Wolfgang
    Wolfgang Riedmann
    Meran, South Tyrol, Italy

    www.riedmann.it - docs.xsharp.it

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 26 Dec 2022 14:54 #24873

    • hilberg.it
    • hilberg.it's Avatar
    • Topic Author


  • Posts: 63
  • Hi,
    I have a real issue with this. For small and simple dialogs I can help myself by resizing dialogs and all included elements. But if I want to add an element to a large dialog from the past, this is a real pain.

    I tried all sorts of resolution and scale factors in my windows settings. The thing is that it seems that I am able to edit some UIs. But others not. What is happening here? The xported UI looks fine in the compiled executable, but if I open and save it in VS Designer, it is messed up in size.

    Do I really have to rearrange ALL exported UIs?! Is this a known Bug from VO? So I would need to know the screen resolution from the machine where this particular Dialog was created? But in VO I was able to edit this Dialogs. I am really confused here and unfortunatly this means a lot of work in an area, where I didin't plan to invest much time (old UI dialogs).

    How can I proceed here?

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 26 Dec 2022 14:57 #24874

    • hilberg.it
    • hilberg.it's Avatar
    • Topic Author


  • Posts: 63
  • ... Were the VO windows created and then exported and edited in X# in the same machine, or at least both had the same screen settings? If not, can you please post the specifications in both machines?

    The dialogs were created and edited on different machines with different settings. I cannot tell you resolutions for the time the dialogs have been created.

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 26 Dec 2022 16:31 #24875

    • Chris
    • Chris's Avatar


  • Posts: 3736
  • HI,

    Can you please send me a few VO modules containing some of those windows, to have a look?
    XSharp Development Team
    chris(at)xsharp.eu

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 27 Dec 2022 11:30 #24880

    • ic2
    • ic2's Avatar


  • Posts: 1573
  • I will dig into it as I seem to remember it could be fixed by changing the resource files. I hope I have some notes of this.

    Dick

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 06 Jan 2023 17:47 #24937

    • hilberg.it
    • hilberg.it's Avatar
    • Topic Author


  • Posts: 63
  • Hi guys,
    good news. Just fixed the issue, by setting visual studio scaling to 100%. See this post learn.microsoft.com/en-us/visualstudio/d...areness?view=vs-2022

    Thanks for your help!

    Please Log in or Create an account to join the conversation.

    Editing exported VO GUI in VS Designer leads to broken gui 06 Jan 2023 18:22 #24939

    • Chris
    • Chris's Avatar


  • Posts: 3736
  • Hi Moritz,

    Thanks a lot for the info, this can be very helpful also to others!

    Btw, when you sent me the sample, I could not reproduce the problem, the window was loading well no matter the windows font size I used. But I just tried now and the problem is very clearly visible, the window does not load well already in the window designer, and also the support windows of the designer (Toolbox, Properties) do not display correctly, either. On the other hand, VO itself still seems to handle this fine, a test window I created in it still loads and gets saved correctly! I'm wondering if it's only under specific circumstances when apps in windows respect or not the new settings. (I was in all cases closing VS/VO before changing the setting, and reopening them afterwards).

    .
    XSharp Development Team
    chris(at)xsharp.eu

    Please Log in or Create an account to join the conversation.

    Last edit: by Chris.
    • Page:
    • 1