SlickEdit Community
Archived Beta Discussions => SlickEdit 201x Beta Discussions => SlickEdit 2019 v24 Beta Discussion => Topic started by: rowbearto on September 12, 2019, 05:51:13 PM
-
On support, look for smartopencol.tar.gz
Follow instructions in the README file to reproduce.
A screenshot of the issue is also in the tarball.
-
Still see this issue in B4
-
I'm not able to reproduce this. For you, only two files are being list. The longer files names FileAppExtended.cc and FileAppExtended.hh aren't being listed for you. For me, all four files get listed and columns are sized ok. Am I missing something? I must be doing something different.
-
You are forgetting to type the dot '.' so that only 2 files get listed, then you will see column is not properly sized.
-
Old eyes ;D
-
:) So were you able to repro it now?
-
Tried reproducing on Ubuntu 18 and CentosOS 6 in a couple different resolutions and no luck. I wasn't able to try the same resolution you are using which definitely could be important. Dont' have a Centos 7 VM at the moment but the exact version of the OS is probably less important for this.
-
hmm, well sometime back I sent you guys a CentOS 7 bare bones VM for a very similar problem with the column sizing. I think Dennis got it working. If you look at this post: https://community.slickedit.com/index.php/topic,15458.15.html
-
I still have a CentOS VM that I sent you guys previously - instructions to use it are on this post: https://community.slickedit.com/index.php/topic,16369.msg63161.html#msg63161
I will send a private message with a link to download the VM.
In a previous time when you tried one of my VMs, to get it to work you had to "disable the network and USB stuff" - https://community.slickedit.com/index.php/topic,15796.msg60303.html#msg60303
-
Look for CentOsVmRob.txt on support, I have a link in there to download the VM.
-
Got the VM running and found two slickedit install. The beta one doesn't seem to have a license file and won't run. The other one is v22. I can run that one. I need root access to install SlickEdit v24 beta and a license file.
-
Nevermind. Got root access. Thought when I tried it the first time it didn't work because it comes back with a $ prompt and I was expecting #
-
Can't seem to ping addresses on our network even if I give an ipaddress. Don't know how to go further with this. I'm definitely not a networking expert.
-
Thanks Clark for going down this road!
Try using "Shared Folders" to install v24 beta. Select VM, click "Settings", then "Shared Folders". See if you can share a folder from your PC to the VM.
-
Another suggestion if you can't get shared folders going is in the Network settings try using a "Bridged Adapter". And in Advanced make sure you choose the correct networking adapter.
-
It's already set to Bridged. I clicked on Advanced. I don't know what to do there. The are some Bandwidth: combo boxes set to Unlimited. I regenerated a Mac address but that didn't help.
-
What about the Shared Folders?
Under "Attached to" in Name: , it should have the name of your ethernet adapter. It may be that it took my adapter and that is why it is not working? In Name: see if you can change it to your ethernet or wifi adapter. You can also try temporarily enabling Adapter 2 and see what it places in Name: and Adapter Type, or disable adapter 1 and try adapter 2.
-
Also, I think I made a mistake earlier when I said the Adapter Type under advanced should match your adapter. I think what is in Advanced is the adapter that the VM emulates. I have this at Intel PRO/1000 MT Desktop (82540EM). What is important I think is that the Name field matches your ethernet/wifi device.
-
Share Folders doesn't seem to work on your VM. I got Share Folders to work on a CentOS 5 VM I have. First time I've ever done that.
-
I tried to do shared folders on a similar VM that I have, I got it to work, I found I had to do the following:
1) When setting up the shared folders in settings, make sure to enable "auto-mount"
2) Inside the VM add "setest" user to "vboxsf" unix group. This can be done by editing as root (using "sudo vi" or one of the older SE installs with sudo) the /etc/group file and changing the last line to add the "setest" user. My "vboxsf" line in /etc/group now looks like: "vboxsf:x:985:setest". The 985 was already in there before I edited, you may have a different number. What is important is to add the ":setest" afterwards.
3) After changing the /etc/group, restart the machine
4) Now you should find the shared folder under /media and you should be able to "cd" into it.
-
I'm using VMWare Workstation Pro. I wouldn't think it would use vboxsf for the group.
I'm not seeing an "auto-mount" option.
-
I'm using Virtualbox, not VMWare workstation. The VM was created with VirtualBox which is free for commercial use, I don't have VMWare workstation - that costs money to buy a license, so I use the "free for commercial use" VirtualBox instead.
The Virtualbox on my PC that I tried with today in 5.2.26, shared folders and networking work. The original post with the VM said 5.2.18. The original post also says: " IMPORTANT: Install Virtualbox extension pack " . The original post also discusses how to import into Virtualbox. Link to "original post": https://community.slickedit.com/index.php/topic,16369.msg63161.html#msg63161
You can download Virtualbox 5.2 series from here: https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
If you continue trying VMWare you may need to install the VMWare tools on the guest? But I think you'll have better luck with VirtualBox.
-
I'll try Virtual Box
-
Able to access the network now.
Reproduced the problem. Must have something to do with the font and/or the resolution. When I change the resolution, I still get the problem. It's clipping about 1 character.
-
Excellent, glad you reproduced it. I’ve seen cases where 3-4 characters are clipped.
-
This is a very odd problem. I'm surprised I can't reproduce this on other platforms. You definitely need to have the files open that are being listed. It's like the bitmap image size isn't being accounted for correctly.
-
The issue seems very similar to what I reported in 2017 here: https://community.slickedit.com/index.php/topic,15458.0.html
I know it was fixed because I haven't had the issue until v24 beta.
So I wonder if that fix was somehow "backed out". I'm sure you could lookup what was done to fix that issue in 2017 and maybe it is still relevant or got removed somehow?
Also see Dennis comment here: https://community.slickedit.com/index.php/topic,15458.msg58993.html#msg58993
Strange problem, given that the clipping seems to relate to the files being open or not.
-
This issue is fixed for the next build.
Looks like a fix was made to v24 that exposed this bug.
Easy to explain the issue. When QFontMetrics (a Qt class) is used, you need to specify the device. If you don't specify the device, you can't rely on the any font calculations because they may be calculated against the wrong device. For example, when printing, you must specify the printer device or you will always get the wrong calculation. In this case, a QWidget must be specified for the device.
What makes this bug so sneaky is that when you don't specify a device, on some platforms it will work all the time. On other platforms, it will work with some displays and not others.
-
Thanks Clark for the persistence and fixing the issue! Really appreciate it!